activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Commented] (AMQ-3879) Temporary queues may be deleted by the wrong connection
Date Fri, 15 Jun 2012 18:45:42 GMT


Gary Tully commented on AMQ-3879:

A workaround is to use watchTopicAdvisories=false on the connection factory.
?jms.watchTopicAdvisories=false on the brokerUrl will do that for you.
In this way, the temp will only be known to the connection that creates it.
> Temporary queues may be deleted by the wrong connection
> -------------------------------------------------------
>                 Key: AMQ-3879
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0
>            Reporter: Daniel Kulp
>            Assignee: Timothy Bish
>             Fix For: 5.7.0
> 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:
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message