You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/12/26 16:28:35 UTC
DO NOT REPLY [Bug 40000] - tomcat / context freezes when hitting maxActive parameter in (oracle) database resource
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40000>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40000
yoavs@computer.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From yoavs@computer.org 2006-12-26 07:28 -------
Don't set maxWait to -1. If you set it to something reasonable, when the pool
is fully busy (i.e. active = maxActive), the pool will wait forever if maxWait =
-1, hence the behavior you're seeing. If I set maxWait to a positive value I
get the exception back right away as expected.
Either way, if there's a bug here, it's much more likely a DBCP bug. It's DBCP
doing the waiting. If you have a stack trace showing hung threads in Tomcat
function calls after the queries have completed (not before), please feel free
to reopen this issue and attach said stack trace.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org