[#AMQ-1176] Using temporary destination across a nework of broker not reliable. - Apache ActiveMQ, Apache ServiceMix, Apache Camel

ActiveMQ

Using temporary destination across a nework of broker not reliable.

Created: 26/Feb/07 10:30 AM Updated: 21/Apr/09 03:49 AM

Return to search

Component/s:

None

Affects Version/s:

4.1.0

Fix Version/s:

4.1.1, 5.0.0

Time Tracking:

Not Specified

Issue Links:

Related

This issue is related to:

~~AMQ-2214~~ Announcement of new temporary queue may lose race with message pointing to it in network of brokers.

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

FishEye

Crucible

Sort Order:

[ Permlink | « Hide ]

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.

[ Permlink | « Hide ]

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.

[ Permlink | « Hide ]

Jonas Lim added a comment - 05/Mar/07 10:05 AM

ported fix to trunk : r514754

[ Permlink | « Hide ]

Jörg Henne added a comment - 21/Apr/09 03:49 AM

~~AMQ-2214~~ might be a regression of ~~AMQ-1176~~.