JBoss Messaging stalls startup synchronizing on an aop AspectManager

Solution Verified - Updated -

Issue

  • Our JBoss start never completes and is perpetually stalled. Thread dumps show the main thread hanging in ServerConnectionFactoryEndpoint.createConnectionDelegateInternal() along with others, for example:
"main" prio=10 tid=0x00007f2e340e1800 nid=0x5199 waiting for monitor entry [0x00007f2e30bf6000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:728)
    - waiting to lock <0x00000000a6dc7f78> (a org.jboss.aop.AspectManager)
    at org.jboss.jms.client.delegate.ClientConnectionDelegate.<clinit>(ClientConnectionDelegate.java)
    at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:296)
    - locked <0x00000000a52dc1f8> (a org.jboss.aop.asintegration.jboss5.ScopedVFSClassLoaderDomain)
    at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:170
...

"WorkManager(2)-1" daemon prio=10 tid=0x00007f2dc90db800 nid=0x52a4 in Object.wait() [0x00007f2e08b56000]
   java.lang.Thread.State: RUNNABLE
    at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:296)
    - locked <0x00000000a6dc7f78> (a org.jboss.aop.AspectManager)
    at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:170)
...

Environment

  • JBoss Enterprise Application Platform (EAP) 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.