tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads)
Date Fri, 23 May 2003 18:42:47 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799

Tomcat dies after being up for a while (complains about maxThreads)

akelley@ecsplus.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From akelley@ecsplus.com  2003-05-23 18:42 -------
I am resolving this bug as INVALID since I think it is a connection pool issue.
 From my research:

A more likely scenario would be that the connections obtained from the pool are
not being returned to the pool properly.  It may take the site some time to show
this problem depending on the number of max connections you allow the pool to
open.  

If the connections are not being returned properly, subsequent calls to the
getConnection method of the pool will wait for a connection to be returned.  If
no connections ever get returned, the method call to getConnection will either
wait until the app server is brought down, or timeout, which could be causing
the problem you describe in your message.  Since I don't believe Tomcat has a
timeout, and since I believe the default max thread for Tomcat is 75, the server
would stop accepting requests at the point when the 75th call was made to
getConnection after all of the available connections were taken.

So after finding one connection that may not have been returned properly, it
seems to work now.  The problem was that the old connection pool was specific
when connections were not being closed.  This one did not give any real errors.

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


Mime
View raw message