commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (DBCP-353) When DB Restarts(Bounce) the number ESTABLISHED DB connections exceeds its maximum configured limit.
Date Sat, 23 Apr 2011 20:54:05 GMT

    [ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023598#comment-13023598
] 

Phil Steitz edited comment on DBCP-353 at 4/23/11 8:54 PM:
-----------------------------------------------------------

Try upgrading to the latest release versions of Commons DBCP (1.3 for JDK 1.4-1.5, 1.4 for
JDK 1.6) and Commons Pool 1.5.6.  If you can produce a test case that shows DBCP creating
more than maxActive connections, please reopen.

      was (Author: psteitz):
    Try upgrading to the latest release versions of Commons DBCP (1.3 for JDK 1.4-1.5, 1.4
for JDK 1.6) and Commons Pool 1.5.4.  If you can produce a test case that shows DBCP creating
more than maxActive connections, please reopen.
  
> When DB Restarts(Bounce) the number ESTABLISHED DB connections exceeds its maximum configured
limit.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DBCP-353
>                 URL: https://issues.apache.org/jira/browse/DBCP-353
>             Project: Commons Dbcp
>          Issue Type: Bug
>            Reporter: Radhika Zawar
>
> We have set Max connections configuration to 100. There was heavy load on application.
When we restarted DB in between, number of connections exceeds from 100 to 200,250...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message