I agree that although your application usage of temporary queues was an
anti-pattern, it shouldn't leak threads as long as you were closing the
connection.
Can you create a JIRA with a small program that demonstrates this issue and we
will investigate further?
Also can you first verify you're
Deleting the TemporaryQueue has no effect. The JMS API spec for
createTemporaryQueue() says:
Create a temporary queue. It's lifetime will be that of the QueueConnection
unless deleted earlier.
I create a connection make the call and close the connection so I should not
need to delete the
So, I modified my code to reuse the same jms connection and temporary queue
within each process that posts messages, and now the thread leakage is gone.
While this change admittedly optimizes the processing, I would still consider
it as a work around for a bug that does not dispose of the
I would have a look in your code to see where you are creating temporary
queues, and make sure you are deleting them when you're finished.
Also it's worth taking a look in JNDI (use jmx-console) to see if there are a
lot of temp queues hanging around.
View the original post :
BTW I would avoid creating a new temp rely queue for every message you send.
This is likely to adversely affect performance.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4126698#4126698
Reply to the post :
Please can you post (or mail me) a complete thread dump of the server when this
problem occurs? (killall -3 java)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4125846#4125846
Reply to the post :
