Connection Timeout, Broker Unsresponsive

Solution Unverified - Updated -


  • The broker cluster connection started getting timeouts This is only reported on a single address, but is impacting the other addresses and applications. The brokers became unresponsive not allowing Jolokia connections for status and causing clients to block on send. The system only recovered when the brokers were restarted
WARN  [org.apache.activemq.artemis.core.server] AMQ222094: Bridge unable to send message Reference[4312994504]:RELIABLE:CoreMessage[messageID=4312736452,durable=true,userID=345d7b71-c9fe-11e8-ac24-74781ae41492,priority=4, timestamp=Sun Oct 07 06:58:59 GMT 2018,expiration=0, durable=true, address=Queue.A.B.CQueue,size=1694,properties=TypedProperties[__AMQ_CID=a992a7e9-c9f9-77e8-ac24-74783ae40490,_AMQ_ROUTING_TYPE=1,_AMQ_ROUTE_TO$.artemis.internal.sf.cluster-DJS-APP.4c013226-c675-11e8-b5cf-b8ca3af6d728=[0000 0000 0000 0134),bytesAsLongs(308]]]@2010168498, will try again once bridge reconnects: ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119014: Timed out after waiting 30,000 ms for response when sending packet 71]


  • Red Hat AMQ
    • 7.2.0

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