Bug 37273 - Under stress, tomcat generates multiple threads/processors for the same request
Summary: Under stress, tomcat generates multiple threads/processors for the same request
Status: RESOLVED INVALID
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Connector:HTTP (show other bugs)
Version: 5.5.9
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-27 17:55 UTC by HannesWeichel
Modified: 2005-10-27 09:59 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description HannesWeichel 2005-10-27 17:55:00 UTC 
I had make a stress-test at our web-application with Grinder and jMeter.
After 5 minutes Tomcat generates several http-80-Processors for one request.
This causes that the corresponding Servlet-class runs multiple 
at the same time (of course with the same sessionID) and 
throws deadlocks in our application.
It must be a Bug because in regular load the 
Tomcat runs (correct)/(dont multiply processors)
Comment 1 Remy Maucherat 2005-10-27 17:59:12 UTC 
You will need to provide a hard proof of this, or investigate more. I think the
thread pool code is explicit enough.

I recommend you use users@tomcat.apache.org to debug this.