[JBoss JIRA] (WFLY-2828) "WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.IllegalStateException" on reload
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-2828:
------------------------------------
Summary: "WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.IllegalStateException" on reload
Key: WFLY-2828
URL: https://issues.jboss.org/browse/WFLY-2828
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transactions
Affects Versions: 8.0.0.CR1
Reporter: Radoslav Husar
Assignee: Tom Jenkinson
About 1/4 times.
{noformat}
13:26:27,786 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: WildFly 8.0.0.Final-SNAPSHOT "WildFly" stopped in 7076ms
13:26:27,787 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: WildFly 8.0.0.Final-SNAPSHOT "WildFly" starting
13:26:27,861 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
13:26:27,874 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
13:26:27,875 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
13:26:27,877 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 39) JBAS010260: Activating JGroups subsystem.
13:26:27,894 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 45) JBAS011800: Activating Naming Subsystem
13:26:27,895 INFO [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem
13:26:27,897 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
13:26:27,897 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Beta33 starting
13:26:27,897 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.0.0.Beta33 starting
13:26:27,900 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.20.Final
13:26:27,900 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
13:26:27,901 WARN [org.wildfly.extension.mod_cluster] (ServerService Thread Pool -- 44) JBAS011706: Metric of type 'mem' is no longer supported and will be ignored.
13:26:27,901 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
13:26:27,901 INFO [org.wildfly.extension.mod_cluster] (ServerService Thread Pool -- 44) JBAS011704: Mod_cluster uses default load balancer provider
13:26:27,901 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:26:27,904 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2
13:26:27,906 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path /home/rhusar/as/build/target/wildfly-8.0.0.Final-SNAPSHOT/welcome-content
13:26:27,909 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017525: Started server default-server.
13:26:27,909 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017531: Host default-host starting
13:26:27,915 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.ejb3.remote.EJBTransactionRecoveryService.getXAResources(EJBTransactionRecoveryService.java:114)
at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:516) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
{noformat}
--
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, 4 months
[JBoss JIRA] (WFLY-2828) "WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.IllegalStateException" on reload
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2828?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-2828:
--------------------------------------
On master as of 2294aa91389bddc8f0a01acbc4aa6ee6cefe0fa0
> "WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.IllegalStateException" on reload
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2828
> URL: https://issues.jboss.org/browse/WFLY-2828
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transactions
> Affects Versions: 8.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Tom Jenkinson
>
> About 1/4 times.
> {noformat}
> 13:26:27,786 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: WildFly 8.0.0.Final-SNAPSHOT "WildFly" stopped in 7076ms
> 13:26:27,787 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015899: WildFly 8.0.0.Final-SNAPSHOT "WildFly" starting
> 13:26:27,861 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 13:26:27,874 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
> 13:26:27,875 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
> 13:26:27,877 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 39) JBAS010260: Activating JGroups subsystem.
> 13:26:27,894 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 45) JBAS011800: Activating Naming Subsystem
> 13:26:27,895 INFO [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem
> 13:26:27,897 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
> 13:26:27,897 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.0.Beta33 starting
> 13:26:27,897 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.0.0.Beta33 starting
> 13:26:27,900 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.20.Final
> 13:26:27,900 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
> 13:26:27,901 WARN [org.wildfly.extension.mod_cluster] (ServerService Thread Pool -- 44) JBAS011706: Metric of type 'mem' is no longer supported and will be ignored.
> 13:26:27,901 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 13:26:27,901 INFO [org.wildfly.extension.mod_cluster] (ServerService Thread Pool -- 44) JBAS011704: Mod_cluster uses default load balancer provider
> 13:26:27,901 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 13:26:27,904 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2
> 13:26:27,906 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path /home/rhusar/as/build/target/wildfly-8.0.0.Final-SNAPSHOT/welcome-content
> 13:26:27,909 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017525: Started server default-server.
> 13:26:27,909 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017531: Host default-host starting
> 13:26:27,915 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.ejb3.remote.EJBTransactionRecoveryService.getXAResources(EJBTransactionRecoveryService.java:114)
> at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:516) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> {noformat}
--
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, 4 months
[JBoss JIRA] (WFLY-2760) Intermittent failure of ExternalContextBindingTestCase
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/WFLY-2760?page=com.atlassian.jira.plugin.... ]
Jan Martiska resolved WFLY-2760.
--------------------------------
Resolution: Done
> Intermittent failure of ExternalContextBindingTestCase
> -------------------------------------------------------
>
> Key: WFLY-2760
> URL: https://issues.jboss.org/browse/WFLY-2760
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.0.0.CR1
> Reporter: Jan Martiska
> Assignee: Jan Martiska
> Priority: Minor
>
> The server setup task sometimes fails to start the ApacheDS server instance because for some reason, BouncyCastle security provider doesn't get registered (it is added through a maven dependency rather than added to the JDK). This leads to a "connection refused" error during the test when it is trying to connect to the LDAP instance.
> It worked for us if we just programatically forced registration of the BouncyCastleProvider before the initialization of ApacheDS.
--
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, 4 months
[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 commented on WFLY-2591:
----------------------------------------
Try: -
./jboss-cli.sh --connect --controller=remoting://10.16.88.187:10100 --command=:shutdown --timeout=10000
> 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: Bug
> 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, 4 months
[JBoss JIRA] (WFLY-2778) CPU load at 99% with WildFly 8 CR1
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-2778?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-2778:
--------------------------------------
Did you manage to get some new stack traces with the upgraded XNIO in place?
> CPU load at 99% with WildFly 8 CR1
> ----------------------------------
>
> Key: WFLY-2778
> URL: https://issues.jboss.org/browse/WFLY-2778
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Environment: $ java -version
> java version "1.7.0_45"
> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
> WildFly 8.0.0.CR1
> XNIO version 3.2.0.Beta4
> Undertow 1.0.0.Beta30
> Reporter: Matthias Richter
> Assignee: Stuart Douglas
> Priority: Blocker
> Attachments: stacktrace-6156.out, stacktrace-6157.out, stacktrace-6158.out, stacktrace-new.out
>
>
> After Undertow included https forwarding features when shipped with Wildfly CR1, we experienced high cpu load on our machines, reproduced on 5 different servers. Up to 3 threads are running wild, sometimes it's just one thread though. On the forum reference there are screenshots from jconsole including stacktraces of the threads.
> https://community.jboss.org/message/853569#853569
--
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, 4 months
[JBoss JIRA] (WFLY-1873) mod_cluster ISE on shutdown
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1873?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-1873:
---------------------------------
Priority: Blocker (was: Major)
Michal is still able to reproduce this in master (jan 28?). Needs a fix.
> mod_cluster ISE on shutdown
> ---------------------------
>
> Key: WFLY-1873
> URL: https://issues.jboss.org/browse/WFLY-1873
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Alpha4
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 8.0.0.Final
>
>
> 16:45:28,305 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (MSC service thread 1-2) Error [MEM: MEM: Can't read node: {4}] sending command DISABLE-APP to proxy localhost/127.0.0.1:6666, configuration will be reset
> 16:45:28,315 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow AJP listener ajp suspending
> 16:45:28,319 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow AJP listener ajp stopped, was bound to /127.0.0.1:8009
> 16:45:28,336 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010418: Stopped Driver service with driver-name = h2
> 16:45:28,344 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow HTTP listener default suspending
> 16:45:28,349 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
> 16:45:38,307 WARN [org.jboss.modcluster.ModClusterService] (MSC service thread 1-2) Failed to drain pending requests from context [org.wildfly.mod_cluster.undertow.UndertowContext@1906d941] within specified timeout: 10 seconds
> 16:45:38,308 WARN [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./clusterbench-ee6-web: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapter.onDeploymentStop(UndertowEventHandlerAdapter.java:137)
> at org.wildfly.extension.undertow.Host$2.invoke(Host.java:138)
> at org.wildfly.extension.undertow.UndertowService.fireEvent(UndertowService.java:168)
> at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:135)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2013) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
--
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, 4 months
[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]: Hello there, could you give us any update on this issue regarding its connection to [WFLY-1597] etc. ?
> 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: Bug
> 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, 4 months
[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:
--------------------------------------
I can confirm this behaviour with WildFly *8.0.0.Final-SNAPSHOT*, my HEAD being {{2294aa91389bddc8f0a01acbc4aa6ee6cefe0fa0}}.
*Server one*, {{port-offset="$\{jboss.socket.binding.port-offset:0\}"}}, expected {{jboss.management.native.port}} is 9999
displays this message during startup:
{noformat}
INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 10.16.88.187:9999
{noformat}
An attempt to shut it down ends up with:
{noformat}
./jboss-cli.sh --connect --controller=10.16.88.187:9999 --command=:shutdown --timeout=10000
{"outcome" => "success"}
{noformat}
*Server two*, {{port-offset="$\{jboss.socket.binding.port-offset:101\}"}}, expected {{jboss.management.native.port}} is 10100
displays this message during startup:
{noformat}
INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 10.16.88.187:10100
{noformat}
An attempt to shut it down ends up with:
{noformat}
./jboss-cli.sh --connect --controller=10.16.88.187:10100 --command=:shutdown --timeout=10000
org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:263)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:226)
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 10.16.88.187:10100
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:990)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:825)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:811)
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:261)
... 8 more
Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://10.16.88.187:10100. 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:967)
... 11 more
Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://10.16.88.187:10100. The connection failed
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
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:169)
at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:129)
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:298)
at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:281)
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:531)
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:79)
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:110)
... 23 more
{noformat}
The funny thing is that the process is actually listening on 10100:
{noformat}
[hudson@perf09 bin]$ netstat -an | grep 10100
tcp 0 0 10.16.88.187:10100 0.0.0.0:* LISTEN
tcp 0 0 10.16.88.187:10100 10.16.88.187:34448 TIME_WAIT
{noformat}
If I kill the Server two process forcefully, port 10100 is released.
> 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: Bug
> 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, 4 months