RE: Is there a limit in the clients connections

In the alpha release, there is a default limit of 20 simultaneous
requests. Subsequent requests are queued until thread becomes available. 
However there is a case where a deadlock can occur - this may be 
what you are experiencing. To verify, try increasing the maximum
no. of threads available to the connector. E.g, in openjms.xml

  <TcpConfiguration port="3035" maxThreads="50"/>

The maxThreads attribute is only available in the alpha version.
In the next release, a different threading strategy will be used i.e,
threads to service requests will be allocated on an as needed
basis.

-Tim

> -----Original Message-----
> From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> Of [email protected]
> Sent: Tuesday, 16 August 2005 10:57 PM
> To: [email protected]
> Subject: [openjms-user] Is there a limit in the clients connections
> 
> I have been making some performance tests with OpenJMS 0.7.7 
> and found that when the number of client connections 
> increases (about 20) a saturation seems to appear and 
> messages are not received any more.
> I was using pub/subscribe scheme.
> The server is in a computer, and publisher and consumers in 
> two other different computers, all are running Win2k.
> Is there any maximum number of simultaneous connections? If 
> so, could it be changed (increased).
> Can I change any configuration parameter to increase the 
> performance of the server?
> 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf