tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse Klaasse <>
Subject Re: IIS 6.0 / JK1.2.25 / Tomcat 5.5.20 - "Service temporary unavailable"
Date Thu, 03 Jul 2008 12:11:06 GMT

Hello Rainer,

Thanks again for your prompt and clear reply. You're helping me a lot!

I have implemented the settings as you suggested (for the datasources of all
8 webapps on my Tomcat server). I need to wait for a restart of the
application before the settings become active, however.
For your information: currently (Tomcat is running fine now) a netstat
command returns about 30 established connections to the database server. I
have lowered the removeAbandonedTimeout setting to 30 seconds instead of 60.

I still have a few questions left;

Why are there no 'AbandonedObjectPool' messages at all when Tomcat is
running fine? I would expect a slowly growing number of locked threads
because of the AbandonedObjectPool. But this not happening. Does this maybe
mean that once it goes wrong, it skyrockets up to the total of 400 locked
threads? And why would that be?

In the STDOUT logs of the past few days, there are no messages at all saying
something like 'DBCP object created'. Shouldn't there be such messages

And finally, would you advise me to install the 1.2.26 version of the
isapi_redirector connector again? As well as the 1.1.12 (or 1.1.13, but I
can't find it for Win64) version of the APR?

Thanks. Jesse.

Rainer Jung-3 wrote:
> So maybe start with something like
> initialSize="10"
> maxActive="50"
> maxIdle"10"
> minIdle="0"
> maxWait="5000" 	
> and check via netstat, how many connections you actually use during peak 
> load. Make sure, your database is correctly configured to handle the 
> maxActive connections.
View this message in context:
Sent from the Tomcat - User mailing list archive at

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message