You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2012/06/12 22:14:42 UTC
[jira] [Created] (AMQ-3879) Temporary queues may be deleted by the
wrong connection
Daniel Kulp created AMQ-3879:
--------------------------------
Summary: 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
[jira] [Commented] (AMQ-3879) Temporary queues may be deleted by
the wrong connection
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295838#comment-13295838 ]
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: https://issues.apache.org/jira/browse/AMQ-3879
> 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:
> 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
[jira] [Commented] (AMQ-3879) Temporary queues may be deleted by
the wrong connection
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295814#comment-13295814 ]
Daniel Kulp commented on AMQ-3879:
----------------------------------
Another note for reference:
The ActiveMQInitialContextFactory only create ActiveMQConnectionFactories (not pooled) and thus is affected by this. This basically means that using JNDI to configure/setup ActiveMQ results in factories/connections that have problems working with the temporary queues. No possible workaround without writing their own InitialContextFactory to handle pooled. Not ideal.
> 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
> 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:
> 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
[jira] [Commented] (AMQ-3879) Temporary queues may be deleted by
the wrong connection
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (AMQ-3879) Temporary queues may be deleted by the
wrong connection
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3879.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Fix and test for this issue.
> 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
> 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:
> 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