JMS Cluster Failover: Recreating non-transacted JMS session after broker failover.

Solution Unverified - Updated -

Issue

  • When using non-transacted sessions, the JMS session does not need to be recreated after a broker failover but doing so results in a exception saying that the session has been failed over. Is this a bug ?
Exception in thread "main" javax.jms.IllegalStateException: has failed over
    at org.apache.qpid.client.AMQSession.acknowledge(AMQSession.java:570)
    at org.apache.qpid.client.message.AMQMessageDelegate_0_10.acknowledge(AMQMessageDelegate_0_10.java:822)
    at org.apache.qpid.client.message.AbstractJMSMessage.acknowledge(AbstractJMSMessage.java:345)
    at com.gs.mrg.eval.JMSReceiveAfterFailoverTest.consumeAndAckMessages(JMSReceiveAfterFailoverTest.java:91)
    at com.gs.mrg.eval.JMSReceiveAfterFailoverTest.run(JMSReceiveAfterFailoverTest.java:123)
    at com.gs.mrg.eval.JMSReceiveAfterFailoverTest.main(JMSReceiveAfterFailoverTest.java:130)

Environment

  • Red Hat Enterprise MRG Messaging
  • qpid-java-0.10-6

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