The fix applied in 6.4.z was https://github.com/jboss-remoting/jboss-remoting/commit/09ccf4c99ce69d3ff55b7bb3c2f5bba10fcbe96a (no jira associated)
Relevant section is: "main" #1 prio=5 os_prio=0 tid=0xf6606c00 nid=0x4066 in Object.wait() [0xf6752000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.xnio.AbstractIoFuture.await(AbstractIoFuture.java:71) - locked <0xe0081818> (a java.lang.Object) at org.xnio.AbstractIoFuture.get(AbstractIoFuture.java:167) - locked <0xe0081818> (a java.lang.Object) at org.jboss.as.protocol.mgmt.FutureManagementChannel.openChannel(FutureManagementChannel.java:154) at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.openChannel(ManagementClientChannelStrategy.java:150) at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.connectionOpened(FutureManagementChannel.java:223) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:79) - locked <0xe007d870> (a org.jboss.as.protocol.ProtocolConnectionManager) at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146) - locked <0xe005a3d0> (a org.jboss.as.controller.client.impl.RemotingModelControllerClient) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) at org.jboss.as.test.shared.ServerReload.waitForLiveServerToReload(ServerReload.java:104) at org.jboss.as.test.shared.ServerReload.executeReloadAndWaitForCompletion(ServerReload.java:72) at org.jboss.as.test.shared.ServerReload.executeReloadAndWaitForCompletion(ServerReload.java:59) at org.jboss.as.test.integration.management.jca.DsMgmtTestBase.reload(DsMgmtTestBase.java:56) at org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.createDataSource(DatasourceXaEnableAttributeTestCase.java:59) at org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestBase.enableLater(DatasourceEnableAttributeTestBase.java:79)
- blocks
-
JBEAP-5295 (7.1.0) Endpoint can be closed before doConnect tasks finished causing AbstractHandleableCloseable.close to wait forever
- Verified
- is related to
-
JBEAP-2017 [GSS](7.0.z) Endpoint can be closed before doConnect tasks finished causing AbstractHandleableCloseable.close to wait forever
- Verified