Christopher Schultz-2 wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kapilok,
On 4/6/2010 11:19 AM, kapilok wrote:
Does Tomcat guarantee recovery in case of this Error?
The JVM/Tomcat should recover in the sense that service threads that
complete their work should go back
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kapilok,
On 4/9/2010 9:46 AM, kapilok wrote:
1. Start Tomcat (with maxThreads=40 )
2. Run JMeter Load (40 concurrent with some ramp up)
- All requests succeed
Good.
3. Now load the database with some heavy process, so CPU consumption is high
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),
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
-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
markt-2 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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kapilok,
On 4/6/2010 11:19 AM, kapilok wrote:
Does Tomcat guarantee recovery in case of this Error?
The JVM/Tomcat should recover in the sense that service threads that
complete their work should go back into the thread pool and accept new
