I suspect you may be running into the problem that the client keeps track of known temporary destinations on the broker, and immediately rejects attempts to produce to temporary destinations that the client doesn't know about, even if they exist on the broker (although that's not the intent).
This includes both a race condition and I suspect just fails when advisories are disabled on the broker; the race condition is due to the following: The client needs to receive the temp destination creation advisory before attempting to send a message to that temporary destination; otherwise the "Cannot publish to a deleted Destination" exception is thrown - by the client library, not the broker That advisory is sent out-of-band (i.e. asynchronously) With that said, the watchTopicAdvisories setting on the client can disable this feature (which I believe is intended to be an optimization). tcp://localhost:61616?jms.watchTopicAdvisories=false See this page for some details: http://activemq.apache.org/advisory-message.html Art P.S. This is my third attempt to reply. Apologies for any duplicates. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
