January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2831) Method Utils.getSecondaryTestAddress(ManagementClient, boolean) doesn't strip square brackets from host IPv6 address

by Josef Cacek (JIRA)

Josef Cacek created WFLY-2831: --------------------------------- Summary: Method Utils.getSecondaryTestAddress(ManagementClient, boolean) doesn't strip square brackets from host IPv6 address Key: WFLY-2831 URL: https://issues.jboss.org/browse/WFLY-2831 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Josef Cacek Assignee: Josef Cacek The striping of square brackets around IPv6 addresses doesn't work in org.jboss.as.test.integration.security.common.Utils.getSecondaryTestAddress(ManagementClient, boolean), it causes failures of AdvancedLdapLoginModuleTestCase. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2745) Typo in jboss-cli help message

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2745?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky updated WFLY-2745: ------------------------------------ Fix Version/s: 8.0.0.Final (was: 8.0.1.Final) > Typo in jboss-cli help message > ------------------------------ > > Key: WFLY-2745 > URL: https://issues.jboss.org/browse/WFLY-2745 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.CR1 > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > Priority: Trivial > Fix For: 8.0.0.Final > > > jboss-cli -h shows the following help message for --controller. > The default controller host is localhost and the port is 9999. > The port number should be 9990 instead of 9999. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2745) Typo in jboss-cli help message

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2745?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky updated WFLY-2745: ------------------------------------ Fix Version/s: 8.0.1.Final Git Pull Request: https://github.com/wildfly/wildfly/pull/5810 > Typo in jboss-cli help message > ------------------------------ > > Key: WFLY-2745 > URL: https://issues.jboss.org/browse/WFLY-2745 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.CR1 > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > Priority: Trivial > Fix For: 8.0.1.Final > > > jboss-cli -h shows the following help message for --controller. > The default controller host is localhost and the port is 9999. > The port number should be 9990 instead of 9999. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2830) Fix org.infinispan.lucene.directory dependencies

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2830?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-2830: ------------------------------- Assignee: Sanne Grinovero (was: Paul Ferraro) > Fix org.infinispan.lucene.directory dependencies > ------------------------------------------------ > > Key: WFLY-2830 > URL: https://issues.jboss.org/browse/WFLY-2830 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Ales Justin > Assignee: Sanne Grinovero > Priority: Blocker > Fix For: 8.0.0.Final > > > The module is missing a bunch of dependencies, > proper module.xml looks like this: https://gist.github.com/alesj/8688428 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2830) Fix org.infinispan.lucene.directory dependencies

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2830?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-2830: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/5808) > Fix org.infinispan.lucene.directory dependencies > ------------------------------------------------ > > Key: WFLY-2830 > URL: https://issues.jboss.org/browse/WFLY-2830 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Ales Justin > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 8.0.0.Final > > > The module is missing a bunch of dependencies, > proper module.xml looks like this: https://gist.github.com/alesj/8688428 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2289) deployed webapp before mod_cluster httpd discovery aren't see by httpd.

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2289?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-2289: -------------------------------------- I cannot reproduce the bug :-( > deployed webapp before mod_cluster httpd discovery aren't see by httpd. > ----------------------------------------------------------------------- > > Key: WFLY-2289 > URL: https://issues.jboss.org/browse/WFLY-2289 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2830) Fix org.infinispan.lucene.directory dependencies

by Ales Justin (JIRA)

Ales Justin created WFLY-2830: --------------------------------- Summary: Fix org.infinispan.lucene.directory dependencies Key: WFLY-2830 URL: https://issues.jboss.org/browse/WFLY-2830 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.CR1 Reporter: Ales Justin Assignee: Paul Ferraro Priority: Blocker Fix For: 8.0.0.Final The module is missing a bunch of dependencies, proper module.xml looks like this: https://gist.github.com/alesj/8688428 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2591) CLI can not connect to the server started with port-offset

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2591?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-2591. ------------------------------------ Resolution: Duplicate Issue > CLI can not connect to the server started with port-offset > ---------------------------------------------------------- > > Key: WFLY-2591 > URL: https://issues.jboss.org/browse/WFLY-2591 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1, 8.0.0.Final > Environment: used actual WildFly Beta from github: > commit 96160520ce245d6a85cbb77cad92a021564aa376 > Date: Wed Nov 20 17:05:00 2013 +0100 > Reporter: Wolf-Dieter Fink > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > > If a standalone server is started with a binding port-offset it is not possible to connect to the native management interface. > To reproduce start a WildFly Beta server (Alpha3 has the same problem) > bin/standalone.sh -Djboss.socket.binding.port-offset=100 > and a cli client: > bin/jboss-cli.sh -c --controller=localhost:10099 > It makes no difference whether the port is changed by port-offset or configuration. > All other ports (i.e. 10090 8180) can be used correct for http-management or ejb invocation. > The server log an ERROR message: > ERROR [org.jboss.remoting.remote.connection] (Remoting "home:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: java.io.IOException: XNIO000804: Received an invalid message length of 1195725856 > The jboss-cli.sh client show: > org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:240) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:218) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:292) > at org.jboss.modules.Main.main(Main.java:455) > Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:10099 > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:960) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:790) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:772) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:238) > ... 8 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:938) > ... 11 more > Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) > at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:166) > at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:127) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 13 more > Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:283) > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:266) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:528) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99) > ... 23 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2829) Optimistic locking w/write skew check requires versioning to be enabled

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/WFLY-2829?page=com.atlassian.jira.plugin.... ] Ales Justin updated WFLY-2829: ------------------------------ Priority: Blocker (was: Major) > Optimistic locking w/write skew check requires versioning to be enabled > ----------------------------------------------------------------------- > > Key: WFLY-2829 > URL: https://issues.jboss.org/browse/WFLY-2829 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 8.0.0.Final > > > Without this, the user cannot configure OPTIMISTIC locking. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2591) CLI can not connect to the server started with port-offset

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-2591?page=com.atlassian.jira.plugin.... ] Michal Babacek commented on WFLY-2591: -------------------------------------- @[~dlofthouse]: THX, it works like a charm :-) > CLI can not connect to the server started with port-offset > ---------------------------------------------------------- > > Key: WFLY-2591 > URL: https://issues.jboss.org/browse/WFLY-2591 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1, 8.0.0.Final > Environment: used actual WildFly Beta from github: > commit 96160520ce245d6a85cbb77cad92a021564aa376 > Date: Wed Nov 20 17:05:00 2013 +0100 > Reporter: Wolf-Dieter Fink > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > > If a standalone server is started with a binding port-offset it is not possible to connect to the native management interface. > To reproduce start a WildFly Beta server (Alpha3 has the same problem) > bin/standalone.sh -Djboss.socket.binding.port-offset=100 > and a cli client: > bin/jboss-cli.sh -c --controller=localhost:10099 > It makes no difference whether the port is changed by port-offset or configuration. > All other ports (i.e. 10090 8180) can be used correct for http-management or ejb invocation. > The server log an ERROR message: > ERROR [org.jboss.remoting.remote.connection] (Remoting "home:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: java.io.IOException: XNIO000804: Received an invalid message length of 1195725856 > The jboss-cli.sh client show: > org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:240) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:218) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:292) > at org.jboss.modules.Main.main(Main.java:455) > Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:10099 > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:960) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:790) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:772) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:238) > ... 8 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:938) > ... 11 more > Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) > at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:166) > at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:127) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 13 more > Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:283) > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:266) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:528) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99) > ... 23 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2014