You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Bruce Snyder (JIRA)" <ji...@activemq.org> on 2006/03/09 00:13:05 UTC

[jira] Closed: (SM-288) Expose Jetty's SocketListener.setMaxThreads() method

     [ http://jira.activemq.org/jira//browse/SM-288?page=all ]
     
Bruce Snyder closed SM-288:
---------------------------

    Resolution: Fixed

> Expose Jetty's SocketListener.setMaxThreads() method  
> ------------------------------------------------------
>
>          Key: SM-288
>          URL: http://jira.activemq.org/jira//browse/SM-288
>      Project: ServiceMix
>         Type: Improvement

>   Components: servicemix-components
>     Reporter: Bruce Snyder
>     Assignee: Bruce Snyder
>      Fix For: 3.0-M1

>
>
> At around 700 concurrent users we are running out of threads:
> 2006-01-24 14:23:03,342 WARN - SocketListener.isOutOfResources(383) | OUT OF THREADS: SocketListener1@10.128.25.62:14000
> This error comes from Jetty because the max number of threads is 256. There is a setter method on the Jetty SocketListener to set the max number of threads and it should be exposed in the HttpConnector, the HttpSoapConnector, the ServerManager and the JettyServer classes. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira