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/07/10 14:54:56 UTC
DO NOT REPLY [Bug 40000] New: - 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
Summary: tomcat / context freezes when hitting maxActive
parameter in (oracle) database resource
Product: Tomcat 5
Version: 5.5.17
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: a.walland@focusmr.com
i have the following in context.xml
<Resource
auth="Container"
name="jdbc/ConnName"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
password="mypass"
maxIdle="10"
maxWait="-1"
validationQuery="SELECT SYSDATE FROM DUAL"
username="myuser"
url="jdbc:oracle:thin:@127.0.0.1:1521:SID"
maxActive="25"
initialSize="10"
/>
benchmarking with siege the tomcat server stops responding when it hits the
maxActive setting. even when the 25 queries finish on the database server tomcat
doesn't seem to return to life ^^.
workaround: set maxActive to "-1" and control maximum active processes with the
"processes" or "sessions" parameter on the oracle server.
i do not know if the same problem exists in conjunction with other databases, i
have only tried it with oracle (10g enterprise and XE)
setup:
apache 1.3.33 on debian stable,
mod-jk connector via ajp13,
latest ojdbc14.jar from oracle.com,
tomcat 5.5.17
jdk 1.5.0_06-b05 BEA Systems, Inc
2.6.8 kernel on a 32 bit x86 smp machine
if any additional information is required i hope i can provide it :)
--
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
DO NOT REPLY [Bug 40000] - tomcat / context freezes when hitting maxActive parameter in (oracle) database resource
Posted by bu...@apache.org.
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