[jira] [Commented] (ARTEMIS-2189) Allow deleting temporary destination when originating session is closed

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-2189:
----------------------------------------------------------

Commit e0a7073884c10d0038d28005308b16760dbe3563 in activemq-artemis's branch refs/heads/master from Justin Graham Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e0a7073 ]

ARTEMIS-2309 TempQueueCleanerUpper instances are leaking

The changes from ARTEMIS-2189 mean that
o.a.a.a.c.s.i.ServerSessionImpl#deleteQueue
is no longer called from the same ServerSessionImpl instance that
created it which means that TempQueueCleanerUpper instances will leak.
To resolve the leak the client will only create a new session when
necessary instead of every time delete() is invoked.


> 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
>             Fix For: 2.7.0
>
>
> 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)