[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1215:
--------------------------------------
We classify this as minor since there's a workaround.
In any case the classification in JIRA is for internal project scheduling purposes and
bears no relation to whether we provide a fix or not to support customers.
Unfortunately JIRA does not provide any priority setting between major and minor.
If you think of the settings as numbers:
blocker = 1
critical = 2;
major = 3
minor = 4
optional = 5
trivial = 6
then this is a 4. I wouldn't read much into the word "minor".
:)
Closing connection does not delete associated TemporaryQueues
-------------------------------------------------------------
Key: JBMESSAGING-1215
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1215
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3
Environment: N/A
Reporter: Mike Clark
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: ReproduceTempQueueLeak.zip, TemporaryQueueDelete.java
When a temporary queue is created, it is not deleted on Connection.close(). This leaves
the queue on the system, but unusable since only consumers that are created from the same
Connection are allowed to consume from a TemporaryQueue (i.e., it is a resource leak).
To reproduce, simply create a Connection, Session, and TemporaryQueue. Close the
Connection and examine the Destinations attribute of the
jboss.messaging:service=ServerPeer MBean. See attached code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira