[
https://issues.apache.org/jira/browse/DBCP-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-299.
------------------------------
Resolution: Duplicate
For 1, you'll need to log the abandoned connections and fix the root causes.
The Oracle JDBC driver is known for keeping them open.
2. Sounds like POOL-107. You could try using dbcp-1.2.2 and pool-1.5.2 rather
than Tomcat's built in copy of DBCP.
If you still see problems, you'll need to provide a test case that we can use
to reproduce the error.
> Number of idle connections exceed MaxIdle parameter Value / Number of active
> connexions on Oracle exceed maxActive parameter value
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DBCP-299
> URL: https://issues.apache.org/jira/browse/DBCP-299
> Project: Commons Dbcp
> Issue Type: Bug
> Environment: Tomcat 5.5
> Java 1.5
> Red Hat Enterprise Linux 5.2
> Oracle : 10.2.0.4.0
> Reporter: Thomassian
>
> We have to disctinct problems.
> We use Tomcat 5.5 and connect to an Oracle 10g database through DBCP.
> 1-We observe that on the DB side, there are many idle connexions (more than
> on DBCP side when we read the numActive and numIdle indicators).
> 2-With maxIdle set to 2, we can have numIdle=3
> For the 1st point, we tried to play with the removeAbandoned and
> removeAbandonedTimeoutParameters but this remained unsuccessfull. Are there
> any other parameters to use ?
> For the 2d point, we have no idea.
> Are these known bugs ?
> Regards,
> Guillaume T
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
