JBoss EAP 6/7 startup/shutdown doesn't complete

Solution Verified - Updated -


  • Startup or Shutdown does not complete on JBoss EAP 6 or 7.
  • Thread dumps show component start ups in the MSC service threads stalled waiting for other components to start, which can't because the MSC thread pool is exhausted:
"MSC service thread 1-1" prio=6 tid=0x000000000a189800 nid=0x1200 in Object.wait() [0x000000000a92d000]
   java.lang.Thread.State: WAITING (on object monitor)
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:485)
    at org.jboss.as.ee.component.BasicComponent.waitForComponentStart(BasicComponent.java:109)
  • JBoss stuck after restart. After restart of JBoss which is running in stand alone mode on one of our server we are unable to access our application running on 8080 port. start script has no port set which makes it run on 8080 default port which was running fine earlier but after restart with no change in any configuration or deployed application server is stuck in logs.


  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In