activemq-dev mailing list archives

[jira] [Commented] (AMQ-3879) Temporary queues may be deleted by the wrong connection

Date

Tue, 12 Jun 2012 20:33:43 GMT

[ https://issues.apache.org/jira/browse/AMQ-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293901#comment-13293901
]
Gary Tully commented on AMQ-3879:
---------------------------------
note to self: A test case that uses two connections, creates a temp on one and a consumer.
verify the advisory propagation via waiting for a failure to delete. then close the second,
should get a failed send to the temp.
> Temporary queues may be deleted by the wrong connection
> -------------------------------------------------------
>
> Key: AMQ-3879
> URL: https://issues.apache.org/jira/browse/AMQ-3879
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.6.0
> Reporter: Daniel Kulp
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira