You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2010/02/15 03:07:28 UTC
[jira] Closed: (DBCP-299) Number of idle connections exceed MaxIdle
parameter Value / Number of active connexions on Oracle exceed maxActive
parameter value
[ https://issues.apache.org/jira/browse/DBCP-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz closed DBCP-299.
----------------------------
> 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.