Hi,

We are running a test case where in the following happens:

1. Client creates a temporary queue and sends the name to a stateless session 
bean
2. The session bean does some work and puts back the result on the temporary 
queue. 
3. The client receives the message.

When testing this behaviour with round about 100 clients (each in a separate 
jvm and each client sending a request to the server once in every 100 seconds, 
there by simulating 1 hit/sec on the server), the server becomes unusable. It 
doesn't die. It still processes the bean request, but was not able to send the 
message back to the client. 

We did a "kill -3" and figured out that there are many threads of ReadTask and 
WriteTask of uil2.SocketManager hanging. After some more testing we have 
noticed that, for every queue that's created, there are 3 ReadTask and 3 
WriteTask threads being created. Once the client is killed, only 1 ReadTask and 
1 WriteTask thread is being released. So, essentially, there are 4 threads (2 
ReadTask and 2 WriteTask) threads hanging around even after the queue (and the 
client) are destroyed.  At the time when the server reaches unusable state, 
there are around 1900 threads in the server. But there is still memory left and 
hence this is not a memory related issue. We are not sure as to what could be 
making the server unresponsive to JMS.  

Is it the number of clients that's causing the issue? 
Why are so many threads getting created for every connection (or queue), which 
are not released when the connection is closed (or killed)?

Can someone throw some light on this?

Thanks,
Kalyan.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857118#3857118

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857118


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to