Mark wrote: > On 05/04/2011 13:21, André Warnier wrote: > > I'll split my response in 2 parts, so that the right person(s) here have > > an easier time to interject their answers/suggestions : > > > > Part 1, for a tomcat expert : > > > > Michael Jerger wrote: > > ... > > > >> So I'm wondering why tomcat needs all these threads and whether I can > >> limit these threads ... (on my system tomcat runs as java). It seams > >> to me that my tomcat rus about 50 threads in idle mode ... thats quite > >> a lot. > > > > It does seem quite a lot to me too, but maybe someone else can give a > > clue. > > Seems high to me too. A thread dump will explain what is going on.
Found the answer allready - in the deployed webapp (liferay) is a c3po - db- connection pool used. Due to another bug (concerning spring and c3po) the configuration was not handeld correctly at this point - so there was the default configuration in place. Default configuration means maxPoolSize = 100 - and every pooled db-connection uses an own thread. So these high thread count had not much to do with tomcat but with the app deploed within - sorry for that. But discussing with Andre lead me to the right point - I used another way of configuration for c3po - now threads are under controll - thank u very much :-)). Michael
signature.asc
Description: This is a digitally signed message part.
