Using temporary destinations across a network of broker can lead to some message not getting delivered due to the way that a temporary destination must first exist on a broker before it accepts a message for it. Due to the timing of some network events, the message may get sent to the destination slightly ahead of the event that creates the temporary destination.
Description
Using temporary destinations across a network of broker can lead to some message not getting delivered due to the way that a temporary destination must first exist on a broker before it accepts a message for it. Due to the timing of some network events, the message may get sent to the destination slightly ahead of the event that creates the temporary destination.
This timing issue also extends out to the JMS clients that will get a JMS exception stating that the destination does not exist yet due to the create event not having been received yet.
Hiram Chirino added a comment - 26/Feb/07 10:32 AM This timing issue also extends out to the JMS clients that will get a JMS exception stating that the destination does not exist yet due to the create event not having been received yet.
Hiram Chirino added a comment - 26/Feb/07 10:34 AM Fixed in http://svn.apache.org/viewvc?view=rev&revision=511082 in the 4.1 branch.
You can avoid getting the 'destination does not exist yet exception' by disabling watchTopicAdvisories feature on the ActiveMQConnectionFactory.
514754
by Jonas Lim
(9 files)
- ported fix to trunk : http://issues.apache.org/activemq/browse/AMQ-1176
New Feature
Resolved
Major
Using temporary destination across a nework of broker not reliable.
