[
https://issues.apache.org/jira/browse/ARTEMIS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707457#comment-16707457
]
Timothy Bish commented on ARTEMIS-2189:
---------------------------------------
A JMS Temporary Destination has a lifetime that is tied to the connection upon
which it was created, not to the Session that was used to create it, so in
actuality the delete method should be usable on a Temporary Destination right
up to the point where the Connection is closed. So the premise of this issue
seems a bit incorrect.
> Deleting JMS temporary destination with a closed session should throw an
> exception
> ----------------------------------------------------------------------------------
>
> Key: ARTEMIS-2189
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2189
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> 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). This can be confusing and/or mask programming errors.
> The [JavaDoc for
> {{javax.jms.TemporaryQueue}}|https://docs.oracle.com/javaee/7/api/javax/jms/TemporaryQueue.html#delete--]
> states that a {{JMSException}} should be thrown, "if the JMS provider fails
> to delete the temporary queue due to some internal error."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
