You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/06/11 22:40:03 UTC

[jira] [Assigned] (AMQ-5015) Temp Queue gets deleted on close of wrong connection

     [ https://issues.apache.org/jira/browse/AMQ-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish reassigned AMQ-5015:
---------------------------------

    Assignee: Timothy Bish

> Temp Queue gets deleted on close of wrong connection
> ----------------------------------------------------
>
>                 Key: AMQ-5015
>                 URL: https://issues.apache.org/jira/browse/AMQ-5015
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.9.0
>            Reporter: Christian Schneider
>            Assignee: Timothy Bish
>             Fix For: 5.11.0
>
>         Attachments: PooledConnectionTempQueueTest.java
>
>
> My scenario is this:
> connection1:
> create temp queue tq1
> send msg to qeue1 with replyTo tq1
> wait for reply on tq1
> connection2:
> receive message on queue1
> send to replyTo address which is tq1
> In some cases the temp queue gets deleted in the close method of connection2.
> The scenario is kind of an edge case as it only happens if I use a PooledConnectionFactory and only if I before my scenario above open a connection and session and close the connection before the session.
> So strictly speaking my code has an error. 
> I think the problem is in the PooledConnection factory. It seems to reuse a connection or session in the wrong way. I will attach a test case



--
This message was sent by Atlassian JIRA
(v6.2#6252)