[AMQ-3879] Temporary queues may be deleted by the wrong connection

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.6.0
• Fix Version/s: 5.7.0
• Assignee: Timothy A. Bish
• Reporter: Daniel Kulp
• Created: 12/Jun/12 20:14
• Updated: 02/May/13 02:30
• Resolved: 12/Jun/12 23:06

Description

While trying to upgrade CXF from 5.4.2 to 5.6, I ran into a slight problem. The fix for AMQ-3038 seems to have caused an issue where closing a connection that has been given an advisory of a temporary queue (AdvisoryConsumer) will result in the temporary queue being delete even if the connection that NEEDS the queue is still using it.

Chatted with gtully a bit:

http://irclogs.dankulp.com/logs/irclogger_log/activemq?date=2012-06-12,Tue&sel=112#l108

This can be reproduced with a CXF checkout (2.6.x-fixes branch) by updating parent/pom.xml to use activemq 5.6 and running the test in rt/transport/jms. The MessageIdAsCorrelationIdJMSConduitTest test fails.

A workaround is to use a PooledConnectionFactory instead of the ActiveMQConnectionFactory. I'll be committing that workaround to trunk so the problem will not be re-producible there.

Issue Links

• relates to: AMQ-4196 Race condition between removal of subscriptions and removal of destinations in a network of brokers