Databases
StackOverflow2013
Postsdbo
POActiveMQ: How to handle broker failovers while using temporary queues
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POActiveMQ: How to handle broker failovers while using temporary queues
    primarykey
    data
    text
    <p>On my JMS applications we use temporary queues on Producers to be able to receive replies back from Consumer applications.</p> <p>I am facing exactly same issue on my end as mentioned in this thread: <a href="http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-3336-Temporary-Destination-errors-on-H-A-failover-in-broker-network-with-Failover-tt-td3551034.html#a3612738" rel="noreferrer">http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-3336-Temporary-Destination-errors-on-H-A-failover-in-broker-network-with-Failover-tt-td3551034.html#a3612738</a></p> <p>Whenever I restarted an arbitrary broker in my network, I was getting many errors like this in my Consumer application log while trying to send reply to a temporary queue:</p> <pre><code>javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://ID:... </code></pre> <p>Then I saw Gary's response there suggesting to use</p> <pre><code>jms.watchTopicAdvisories=false </code></pre> <p>as a url param on the client <code>brokerURL</code>. I promptly changed my client broker URLs with this additional parameter. However now I am seeing errors like this when I restart my brokers in network for this failover testing:</p> <pre><code>javax.jms.JMSException: The destination temp-queue: //ID:client.host-65070-1308610734958-2:1:1 does not exist. </code></pre> <p>I am using ActiveMQ 5.5 version. And my client broker URL looks like this:</p> <pre><code>failover:(tcp://amq-host1:61616,tcp://amq-host2.tred.aol.com:61616,tcp://amq-host3:61616,tcp://amq-host4:61616)?jms.useAsyncSend=true&amp;timeout=5000&amp;jms.watchTopicAdvisories=false </code></pre> <p>Additionally here is my activemq config XML for one of the 4 brokers: <a href="http://activemq.2283324.n4.nabble.com/file/n3612738/amq1.xml" rel="noreferrer">amq1.xml</a></p> <p>Can someone here please look into this problem and suggest me what mistake I am making in this setup. </p> <h1>Update:</h1> <p>To clarify further on how I am doing request-response in my code:</p> <ol> <li>I already use a per producer destination (i.e. temporary queue) and set this in reply-to header of every message.</li> <li>I am already sending a per message unique correlation identifier in JMSCorrelationID header.</li> <li>As far as I know even Camel and Spring are also using temporary queue for request-response mechanism. Only difference is that Spring JMS implementation creates and destroys temporary queue for every message whereas I create temporary queue for the lifetime of the producer. This temporary queue is destroyed when client (producer) app shutsdown or by the AMQ broker when it realizes there are no active producer attached with this temporary queue.</li> <li>I am already setting a message expiry on each message on Producer side so that message is not held up in a queue for too long (60 sec).</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRoman C
    1. USanubhava
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POActiveMQ: How to handle broker failovers while using temporary queues
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POActiveMQ: How to handle broker failovers while using temporary queues
      1. USanubhava
      1. VTBountyStart
    3. VO
      singulars
      1. POActiveMQ: How to handle broker failovers while using temporary queues
      1. USanubhava
      1. VTFavorite
    1. COIs the new `JMSException` just logged or thrown into your client code? Also, is the exception thrown on every message the client sends to the broker, or does the exception stop when the failover completes? (I.e. Is the exception only thrown during the time when the client is not connected?)
      singulars
      1. POActiveMQ: How to handle broker failovers while using temporary queues
      1. USBringer128
    2. COThere [seems to be](http://activemq.apache.org/advisory-message.html#AdvisoryMessage-Disablingadvisorymessages) a couple of things you need to do in addition to the `jms.watchTopicAdvisories=false`, i.e. `<broker advisorySupport="false">` in your XML configuration, and statically configuring your network. (your amq1.xml file gives me a 404 Not Found)
      singulars
      1. POActiveMQ: How to handle broker failovers while using temporary queues
      1. USopyate
    3. CO@Bringer128: Thanks for your comment. That JMS exception is thrown on the other AMQ broker where producer connects after reconnect. And once this happens JMS producer just stops receiving any responses from consumer since AMQ broker just cannot send the reply back to producer with the above JMS Exception.
      singulars
      1. POActiveMQ: How to handle broker failovers while using temporary queues
      1. USanubhava
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload