Bug 36470 - Connections not release on encountering exception.
Summary: Connections not release on encountering exception.
Status: RESOLVED WORKSFORME
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Connector:AJP (show other bugs)
Version: 5.0.28
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-02 09:25 UTC by Nags
Modified: 2006-10-20 18:10 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 Nags 2005-09-02 09:25:58 UTC 
When a valve throws an unhandled exception during run time, it seems like the 
connector does not release the socket immediately. If a number of these 
instances occur, we get into a state where, unless the socket timeout is not 
reached, it is not possible to get another connection to the web server.

The server starts returning HTTP 503 in this case.
Comment 1 Yoav Shapira 2005-10-16 07:24:14 UTC 
Can you provide us with steps to reproduce this, please?
Comment 2 Mark Thomas 2006-10-20 18:10:34 UTC 
I have tested this using JMeter with the latest code from SVN and the number of
threads remains roughly equal to the number of simultaneous connections.
Therefore, as far as I can tell this has been fixed.

Be aware that another 5.0.x release is unlikely.