[ 
https://issues.apache.org/jira/browse/ARTEMIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707697#comment-16707697
 ] 

ASF GitHub Bot commented on ARTEMIS-2189:
-----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2448

    ARTEMIS-2189 allow deleting temp dest when session is closed

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-2189

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2448.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2448
    
----
commit ff4176573105fbefb57ec23f2a446f434437ca79
Author: Justin Bertram <jbertram@...>
Date:   2018-12-03T19:44:32Z

    ARTEMIS-2189 allow deleting temp dest when session is closed

----


> Allow deleting temporary destination when originating session is closed
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-2189
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2189
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.6.3
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>
> If a client closes its JMS session (intentionally or not) and then invokes 
> {{javax.jms.TemporaryQueue.delete()}} or 
> {{javax.jms.TemporaryTopic.delete()}} these methods will return without 
> actually deleting the destination (because the underlying session was 
> closed).  The JMS spec states that the lifetime of a temporary destination is 
> tied to the connection rather than the session so even after the session is 
> closed it should still be possible to delete the temporary destination.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to