Tim,
I emailed a thread dump to [EMAIL PROTECTED]
I have been able to narrow my parameters and get a reproducible environment for
this issue.
I wrote a webapp program that queues up messages to the clustered queue. It
uses the default provider so it is always queueing to its partial queue. This
is executed on AppSvr1.
The consumers are connected to AppSvr2, so all messages posted get sucked from
AppSvr1 to AppSvr2. In this configuration both servers leak the same number of
threads, one for each message.
However, when I changed the request message to not specify a temporary queue
for the return message I get no leakage. My consumer has a default queue to
send responses if a response queue is not specified in the message. All the
response messages end up on the default response queue.
So to summarize:
Cluster has 2 JBoss servers AppSrv1 & AppSrv2.
| AppSrvr1 posts messages to [partial queue 1] requestQueue.
| Messages are sucked over to AppSvr2 [partial queue 2] requestQueue
| Consumers consumes from [partial queue 2] requestQueue
|
| a) When a temporary response queue is specified, all response
| messages end up back on AppSvr1, but both servers leak one
| thread per message.
|
| b) When no response queue is specified then all responses end up on
| AppSvr2 [partial queue 2] responseQueue (the default) and no
| threads are leaked.
|
It would appear that the issue is somewhere in the code that deals with the
temporary queues.
I hope this helps to resolve this.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126682#4126682
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126682
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
