tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Recover from SEVERE: All threads (400) are currently busy, waiting. Increase maxThreads (400) or check the servlet status
Date Tue, 06 Apr 2010 14:43:16 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark,

On 4/6/2010 8:54 AM, Mark Thomas wrote:
> On 06/04/2010 13:03, kapilok wrote:
>>
>> I need to restart tomcat after the error:
>> Recover from SEVERE: All threads (400) are currently busy, waiting. Increase
>> maxThreads (400) or check the servlet status
>>
>> This happens when the Database gets overloaded and responds slowly.
>>
>> I would like tomcat to recover (without having to restart), once I have
>> solved the database overload issue (which takes a few minutes).
>>
>> I am using Tomcat 5.5.20 on Windows Server 2003.
>>
>> Please advise.
> 
> Tomcat shouldn't need to restart in this case. It should recover
> automatically. If it doesn't, that suggests your applciation is not
> handling the lack of response from the database in a graceful manner.

+1

Sounds like deadlock on the application to me: this would tie-up threads
forever (the definition of deadlock: duh).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAku7SIQACgkQ9CaO5/Lv0PCNuwCgupCY3VQUDaVv2cecPeDbtvIr
rXcAnjlRDztDldq3oBAzZwoLIvkcA+r7
=e/vU
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message