[jboss-jira] [JBoss JIRA] (WFLY-4113) 8.2.0.Final build hangs
[
https://issues.jboss.org/browse/WFLY-4113?page=com.atlassian.jira.plugin....
]
Peter Major commented on WFLY-4113:
-----------------------------------
This is what I had done:
{noformat}
# Build byteman 2.0.0, since it is not available in any of the repositories defined by
jboss-remoting's POM
git clone https://github.com/bytemanproject/byteman.git
cd byteman
git checkout 2.0.0
mvn clean install
# We can build jboss-remoting now
git clone https://github.com/jboss-remoting/jboss-remoting.git
cd jboss-remoting
git checkout 4.0
# Need to build jboss-remoting with english locale, because "Connection refused"
is hardcoded in org.jboss.remoting3.test.RemoteChannelTest
LC_ALL=en_US.UTF-8 mvn clean install
{noformat}
After modifying the WildFly pom to include 4.0.7.Final-SNASHOT, I've got a new hanging
test in wildfly-domain-management now instead:
{noformat}
Running
org.jboss.as.domain.management.security.realms.PropertiesAuthenticationDigestedTestCase
{noformat}
Now I can only wonder if the release was built without executing tests...
8.2.0.Final build hangs
-----------------------
Key: WFLY-4113
URL: https://issues.jboss.org/browse/WFLY-4113
Project: WildFly
Issue Type: Feature Request
Components: Test Suite
Affects Versions: 8.2.0.Final
Reporter: Peter Major
Assignee: David Lloyd
Attachments: jstack.txt
When trying to build 8.2.0.Final locally, my build just hangs indefinitely while
executing a unit test in the controller module:
{noformat}
Running org.jboss.as.controller.ModelControllerClientTestCase
{noformat}
Running jstack against the build suggests that there is a deadlock between
{noformat}
- waiting to lock <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
at
org.jboss.remoting3.remote.RemoteConnectionChannel.closeMessages(RemoteConnectionChannel.java:560)
at
org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:542)
at
org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
at
org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:423)
- locked <0x00000007b8d8e6f8> (a java.util.ArrayDeque)
at
org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:232)
{noformat}
and
{noformat}
- waiting to lock <0x00000007b8d8e6f8> (a java.util.ArrayDeque)
at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:122)
at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:154)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:122)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:115)
at org.xnio.streams.BufferPipeOutputStream.flush(BufferPipeOutputStream.java:139)
- locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:157)
- locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
at org.jboss.remoting3.remote.OutboundMessage.close(OutboundMessage.java:283)
- locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
at java.io.FilterOutputStream.close(FilterOutputStream.java:160)
{noformat}
Preferably locks should be obtained in the same order across the different code paths to
prevent deadlocks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)