[
https://issues.apache.org/jira/browse/ARTEMIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707736#comment-16707736
]
ASF GitHub Bot commented on ARTEMIS-2189:
-----------------------------------------
Github user jbertram commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2448#discussion_r238422596
--- Diff:
tests/jms-tests/src/test/java/org/apache/activemq/artemis/jms/tests/TemporaryDestinationTest.java
---
@@ -265,6 +266,126 @@ public void testTemporaryQueueDeleted() throws
Exception {
}
}
+ @Test
+ public void testTemporaryQueueDeletedAfterSessionClosed() throws
Exception {
--- End diff --
The issue here is not with the broker but with the core client. Therefore,
I'm not sure it makes sense to test other clients on this particular use-case.
> 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)
