activemq-dev mailing list archives

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

    [ 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

        

Mime
View raw message