[jboss-jira] [JBoss JIRA] (WFLY-2675) Boot (???) deadlock

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFLY-2675.
------------------------------------

    Resolution: Done


Resolved with upgrade to MSC 1.2.0.CR2 or later. Master is now on .Final.
                
> Boot (???) deadlock
> -------------------
>
>                 Key: WFLY-2675
>                 URL: https://issues.jboss.org/browse/WFLY-2675
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Critical
>             Fix For: 8.0.0.Final
>
>
> A deadlock occurred during a testsuite/domain run:
> http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=7356&buildTypeId=WFPR
> The test hung during domain shutdown:
> {code}
> at org.jboss.as.test.integration.domain.management.util.ProcessWrapper.waitFor(ProcessWrapper.java:97)
> 	at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.stop(DomainLifecycleUtil.java:312)
> 	- locked <0xa7ac7318> (a org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil)
> 	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.stop(DomainTestSupport.java:370)
> 	at org.jboss.as.test.integration.domain.ServerManagementTestCase.tearDownDomain(ServerManagementTestCase.java:116)
> {code}
> It's possible that's just when the test client hung, and the issue may have occurred at some earlier point. On the thread dump of all processes, one of the servers under the slave HC reported this:
> {code}
> Found one Java-level deadlock:
> =============================
> "Controller Boot Thread":
>   waiting to lock monitor 0x9a2566e0 (object 0xafdc6028, a org.jboss.msc.service.ServiceControllerImpl),
>   which is held by "MSC service thread 1-1"
> "MSC service thread 1-1":
>   waiting to lock monitor 0x9a2575b8 (object 0xb014ea70, a java.lang.Object),
>   which is held by "Controller Boot Thread"
> Java stack information for the threads listed above:
> ===================================================
> "Controller Boot Thread":
> 	at org.jboss.msc.service.ServiceControllerImpl.removeMonitorNoCallback(ServiceControllerImpl.java:1486)
> 	- waiting to lock <0xafdc6028> (a org.jboss.msc.service.ServiceControllerImpl)
> 	at org.jboss.msc.service.StabilityMonitor.clear(StabilityMonitor.java:175)
> 	- locked <0xb014ea70> (a java.lang.Object)
> 	at org.jboss.as.server.BootstrapListener.printBootStatistics(BootstrapListener.java:70)
> 	at org.jboss.as.server.ServerService.boot(ServerService.java:345)
> 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256)
> 	at java.lang.Thread.run(Thread.java:724)
> "MSC service thread 1-1":
> 	at org.jboss.msc.service.StabilityMonitor.removeControllerNoCallback(StabilityMonitor.java:151)
> 	- waiting to lock <0xb014ea70> (a java.lang.Object)
> 	at org.jboss.msc.service.ServiceControllerImpl.transition(ServiceControllerImpl.java:688)
> 	at org.jboss.msc.service.ServiceControllerImpl$RemoveTask.run(ServiceControllerImpl.java:2267)
> 	- locked <0xafdc6028> (a org.jboss.msc.service.ServiceControllerImpl)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:724)
> {code}

--
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