https://issues.apache.org/bugzilla/show_bug.cgi?id=53836
Priority: P2
Bug ID: 53836
Assignee: dev@tomcat.apache.org
Summary: This question is about Bug ID 40000
Severity: normal
Classification: Unclassified
OS: Linux
Reporter: npun...@consultantemail.com
Hardware: PC
Status: NEW
Version: 7.0.26
Component: Catalina
Product: Tomcat 7
There was a workaround provided for this situation with Tomcat version 5.5.
Just wanted to confirm if it was ever fixed in the later versions.
We are suspecting a similar issue in our environment with Tomcat 7.0.26 and
would like to know the following:
Under a situation where Tomcat's active jdbc connections = maxActive and
maxWait="-1", if Tomcat stops responding, what would be the status of the
Tomcat manager application. Will it be accessible? This will confirm if we are
hitting this bug or not as the regular application was not accessible during
the Incident but Tomcat manager application was accessible. We had to restart
the Tomcat instance to fix the situation.
Here's our config:
<Resource name="xxxx"
auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@xxxxxxxxxx:1523:SID"
username="some_user"
password="xxxxxxx"
maxActive="12"
validationQuery="SELECT 1 FROM DUAL"
accessToUnderlyingConnectionAllowed="true"
testOnBorrow="true"
maxIdle="10"
maxWait="-1" />
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
