Re: Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

On Sep 17, 2007, at 12:56 PM, David Jencks wrote: On Sep 17, 2007, at 11:44 AM, Joe Bohn wrote: David, Should we expose these attributes in the config.xml and config- substitions.properties in our default assemblies so that they are more easily edited? https://issues.apache.org/jira/br

Re: Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

On Sep 17, 2007, at 11:44 AM, Joe Bohn wrote: David, Should we expose these attributes in the config.xml and config- substitions.properties in our default assemblies so that they are more easily edited? https://issues.apache.org/jira/browse/GERONIMO-3475 Also, is the current default of 5

Re: Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

David, Should we expose these attributes in the config.xml and config-substitions.properties in our default assemblies so that they are more easily edited? Also, is the current default of 500 still appropriate? It looks like this was changed from 300 to 500 as part of your work to hook the

Re: Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

Hello David, thanks much for the tip, this will help saving resources on our notebook installations with Little-G. Thanks, Mario David Jencks wrote: Thanks for pointing out that this is overly difficult to configure. In your var/config/config.xml add this to the rmi-naming module element

Re: Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

Thanks for pointing out that this is overly difficult to configure. In your var/config/config.xml add this to the rmi-naming module element 5000 ${threadPoolSize} and add this in var/config/config-substitutions.properties threadPoolSize=100 (or whatever value you want)

Re: Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

Ok, now that I run Geronimo 2.0.1 with console I see the max thread setting of 500. The Little-G Version is also set to this default max thread count. The question for me is now why this increase in max thread count compared with the 1.1 version? Some systems like HP-UX have a default of 128 threa

Threads not released/reused in Geronimo 2.0.1 and Jetty, was: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

The increasing creation of Threads happens also when I start the default Geronimo/Jetty 2.0.1 distribution. Even the usage of the console leads to creation of new Threads and none of the existing Threads will be reused. I tested it in the following environment: Windows XP, Java 1.6.0_02 HP-UX, J