[JBoss JIRA] Created: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
1:44 p.m.
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
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
1:46 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Mike Clark updated JBMESSAGING-1215:
------------------------------------
Attachment: TemporaryQueueDelete.java
Code to reproduce the problem.
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
Attachments: 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
1:51 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Mike Clark updated JBMESSAGING-1215:
------------------------------------
Attachment: ReproduceTempQueueLeak.zip
Eclipse project reproducing problem for convenience.
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
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
8:11 a.m.
New subject: [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:
--------------------------------------
The actual queue *is* deleted - it is just the destination object remains registered in
JNDI - giving a small (few bytes?) resource leak.
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
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
8:11 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Tim Fox updated JBMESSAGING-1215:
---------------------------------
Priority: Minor (was: Major)
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
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
12:15 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=comments#action_1... ]
P Duffy commented on JBMESSAGING-1215:
--------------------------------------
I'm not comfortable with the "minor" classification. We'll have
messaging clients frequently coming and going to our HA app. Any leak is a concern.
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
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
4:10 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Tim Fox updated JBMESSAGING-1215:
---------------------------------
Fix Version/s: Stable branch
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
7:26 a.m.
New subject: [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
4:54 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Tim Fox updated JBMESSAGING-1215:
---------------------------------
Fix Version/s: 1.4.0.SP3.CP01
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, 1.4.0.SP3.CP01
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
3:05 p.m.
New subject: [JBoss JIRA] Resolved: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Mike Clark resolved JBMESSAGING-1215.
-------------------------------------
Resolution: Done
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: 1.4.0.SP3.CP01, 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
9:06 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Mike Clark reopened JBMESSAGING-1215:
-------------------------------------
Assignee: Mike Clark (was: Tim Fox)
Tim suggested moving the test case to
org.jboss.test.messaging.jms.TemporaryDestinationTest.java. Reopening to track this
change.
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: Mike Clark
Priority: Minor
Fix For: Stable branch, 1.4.0.SP3.CP01
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
9:35 p.m.
New subject: [JBoss JIRA] Resolved: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Mike Clark resolved JBMESSAGING-1215.
-------------------------------------
Resolution: Done
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: Mike Clark
Priority: Minor
Fix For: 1.4.0.SP3.CP01, 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
4:05 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Tim Fox closed JBMESSAGING-1215.
--------------------------------
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: Mike Clark
Priority: Minor
Fix For: 1.4.0.SP3.CP01, 1.4.1.beta2
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
4:05 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1215?page=all ]
Tim Fox updated JBMESSAGING-1215:
---------------------------------
Fix Version/s: 1.4.1.beta2
(was: Stable branch)
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: Mike Clark
Priority: Minor
Fix For: 1.4.0.SP3.CP01, 1.4.1.beta2
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
6724
days inactive
6780
days old
13 comments
3 participants
participants (3)
-
Mike Clark (JIRA) -
P Duffy (JIRA)
-
Tim Fox (JIRA)