You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Radhika Zawar (JIRA)" <ji...@apache.org> on 2011/02/10 06:58:57 UTC
[jira] Created: (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
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
[jira] Commented: (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Radhika Zawar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999241#comment-12999241 ]
Radhika Zawar commented on DBCP-353:
------------------------------------
Any updates in this issue?
> 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
[jira] Commented: (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Radhika Zawar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993408#comment-12993408 ]
Radhika Zawar commented on DBCP-353:
------------------------------------
dbcp version - commons-dbcp-1.2.2
pool version - commons-pool-1.3
We are counting connections using command
netstat -an | grep <host>.1521 | grep ESTABLISHED | wc -l
--------------
Following are the actual steps that were performed
1. Run the load
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
100
2 . Shutdown DB
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
3
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
0
3. start DB
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
77
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
77
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
83
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
112
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
133
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
154
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
191
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
128
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
128
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
129
bash-3.00# netstat -an | grep 1521 | grep ESTABLISHED | wc -l
128
> 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
[jira] [Closed] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz closed DBCP-353.
----------------------------
Resolution: Not A Problem
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
[jira] [Issue Comment Edited] (DBCP-353) When DB Restarts(Bounce)
the number ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Radhika Zawar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009555#comment-13009555 ]
Radhika Zawar commented on DBCP-353:
------------------------------------
Hi,
Can you please let me know the solution to this issue.
Thanks.
> 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
[jira] [Reopened] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz reopened DBCP-353:
------------------------------
> 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
[jira] Commented: (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993086#comment-12993086 ]
Phil Steitz commented on DBCP-353:
----------------------------------
What versions of Commons DBCP and Pool are you using and how are your counting connections? Is DBCP itself reporting the excessive number of connections?
> 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
[jira] Commented: (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Radhika Zawar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993361#comment-12993361 ]
Radhika Zawar commented on DBCP-353:
------------------------------------
dbcp version - commons-dbcp-1.2.2
pool version - commons-pool-1.3
We are counting connections using command
netstat -an | grep <host>.1521 | grep -v ESTABLISHED | wc -l
> 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
[jira] [Reopened] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz reopened DBCP-353:
------------------------------
> 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
[jira] [Reopened] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz reopened DBCP-353:
------------------------------
Sorry to keep flip-flopping on this; but it now occurs to me that this could be related to DBCP-342.
Do you have minIdle and timeBetweenEvictionRunsMillis both set to positive values?
> 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
[jira] [Updated] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz updated DBCP-353:
-----------------------------
Fix Version/s: 1.4.1
1.3.1
> 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
> Fix For: 1.3.1, 1.4.1
>
>
> 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
[jira] [Closed] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz closed DBCP-353.
----------------------------
Resolution: Cannot Reproduce
> 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
[jira] Updated: (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Radhika Zawar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radhika Zawar updated DBCP-353:
-------------------------------
Comment: was deleted
(was: dbcp version - commons-dbcp-1.2.2
pool version - commons-pool-1.3
We are counting connections using command
netstat -an | grep <host>.1521 | grep -v ESTABLISHED | wc -l)
> 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
[jira] [Closed] (DBCP-353) When DB Restarts(Bounce) the number
ESTABLISHED DB connections exceeds its maximum configured limit.
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz closed DBCP-353.
----------------------------
Resolution: Fixed
> 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