AMQ Resource adapter us hung while graceful Jboss shutdown

Solution Verified - Updated -


  • JBoss A-MQ resource adapter is configured in JBoss EAP 6 to communcate with remote JBoss A-MQ server. During greaceful shutdown we see that JBoss EAP server hangs. In the thread dumps we could see that one of AMQ RAR threads is stuck with following stack:
ServerService Thread Pool -- 102" prio=10 tid=0x00007fbc28167800 nid=0x7ed0 in Object.wait() [0x00007fbc682f6000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
    at java.lang.Object.wait(Native Method)
    - waiting on <0x0000000707694a38> (a java.util.concurrent.atomic.AtomicBoolean)
    at org.apache.activemq.ra.ServerSessionPoolImpl.close(
    - locked <0x0000000707694a38> (a java.util.concurrent.atomic.AtomicBoolean)
    at org.apache.activemq.ra.ActiveMQEndpointWorker.stop(
    - locked <0x00000007071d9548> (a java.lang.String)
    at org.apache.activemq.ra.ActiveMQResourceAdapter.endpointDeactivation(
    at org.jboss.jca.core.rar.EndpointImpl.deactivate(
  • Jira AMQ-5038 is filed for the same, however it is fixed in ActiveMQ 5.10.


  • Red Hat JBoss A-MQ
    • 6.0

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

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content