HornetQ JMS client fails to reconnect to the JMS provider
Issue
A remote HQ JMS client will fail to trigger its connection-factory-retry-logic when the physical machine on which the remote HQ instance is running is down. For example, consider a JMS client that is publishing messages to a remote HQ/EAP instance. Now shutdown the remote server itself. The JMS client will receive the following exception:
Caused by: javax.jms.JMSException: Timed out waiting for response when sending packet 71
at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:276)
at org.hornetq.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:287)
at org.hornetq.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:142)
at org.hornetq.jms.client.HornetQMessageProducer.doSend(HornetQMessageProducer.java:451)
at org.hornetq.jms.client.HornetQMessageProducer.send(HornetQMessageProducer.java:246)
at org.hornetq.jms.client.HornetQMessageProducer.publish(HornetQMessageProducer.java:277)
at com.aaa.impl.JMSSender.send(JMSSender.java:377)
If the client were to re-try the message send, it will receive the exception again.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 5.1.0
- HornetQ
- 2.2.5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
