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

Re: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

The new Treads are created by more than one Servlet requests when loading a page. The page itself and also serving some static files. The new Threads appear all at the same time because of a synchronized block in SelectChannelEndPoint.undispatch(); Which is called at the line number mentioned in m

Re: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

Ok, I will download or checkout the Jetty 6.1.5 sources to do some further investigation on it. Thanks, Mario Paul McMahan wrote: Mario, thanks for doing the extra debugging to narrow down where the problem is at. Yes the jetty version is 6.1.5. You can also find the version number of a c

Re: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

Mario, thanks for doing the extra debugging to narrow down where the problem is at. Yes the jetty version is 6.1.5. You can also find the version number of a component in the admin console's System modules portlet or by the directory name in Geronimo's repository, in this case $G/repos

Re: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

On Sep 14, 2007, at 11:34 AM, Mario Ruebsam wrote: I did some debugging and followed the code until: SelectChannelConnector$ConnectorEndPoint(SelectChannelEndPoint).run () line: 422 when this line is called the Treads will be created. Nice. Thanks for digging into this Mario! I guess t

Re: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

I did some debugging and followed the code until: SelectChannelConnector$ConnectorEndPoint(SelectChannelEndPoint).run() line: 422 when this line is called the Treads will be created. I guess this is Jetty code because I could not found it in the Geronimo sources. Which Jetty version is used is

Re: Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

I did some debugging and followed the code until: SelectChannelConnector$ConnectorEndPoint(SelectChannelEndPoint).run() line: 422 when this line is called the Treads will be created. I guess this is Jetty code because I could not found it in the Geronimo sources. Which Jetty version is used is

Creation of new threads after closing response writer in Servlet in Little-G Jetty 2.0.1

Hello, after migrating successful from Little-G Jetty 1.1 to Little-G Jetty 2.0.1 I detected some strange behavior when closing the Servlets response writer. Every time the writer is closed Geronimo or Jetty creates 10 new Threads in the DefaultThreadPool. The code snippet is below. In G 1.1 the