Mark wrote:
> On 05/04/2011 13:21, Andr=C3=A9 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 :
> >=20
> > Part 1, for a tomcat expert :
> >=20
> > Michael Jerger wrote:
> > ...
> >=20
> >> 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.
> >=20
> > It does seem quite a lot to me too, but maybe someone else can give a
> > clue.
>=20
> Seems high to me too. A thread dump will explain what is going on.
=46ound the answer allready - in the deployed webapp (liferay) is a c3po - =
db-
connection pool used.=20
Due to another bug (concerning spring and c3po) the configuration was not=20
handeld correctly at this point - so there was the default configuration in=
=20
place.
Default configuration means maxPoolSize =3D 100 - and every pooled db-conne=
ction=20
uses an own thread. So these high thread count had not much to do with tomc=
at=20
but with the app deploed within - sorry for that.
But discussing with Andre lead me to the right point - I used another way o=
f=20
configuration for c3po - now threads are under controll - thank u very much=
=20
:-)).
Michael
|