[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506646 ] Phil Steitz commented on DBCP-212: -- PoolableConnectionFactory.makeObject() has been synchronized since the initial co

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490930 ] Marcos Sanz commented on DBCP-212: -- Regarding concurrency control of GenericObjectPool, I have submitted a patch (see

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488664 ] Marcos Sanz commented on DBCP-212: -- Yes, I also have the feeling that DBCP-205 is an aspect of this issue, appearing

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488252 ] Phil Steitz commented on DBCP-212: -- Thanks, Marcos. Really appreciate your feedback and help chasing this down. I s

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488048 ] Marcos Sanz commented on DBCP-212: -- Not true. Even if I drop the System.out call and maintain the getMaxActive(), the

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487994 ] Phil Steitz commented on DBCP-212: -- Thanks. By adding the System.out, I can reproduce the symptoms. You are correct

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487805 ] Marcos Sanz commented on DBCP-212: -- Indeed, the problem is triggered by the synchronized methods in GenericObjectPool

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487735 ] Marcos Sanz commented on DBCP-212: -- The issue can be reproduced with pool 1.2/dbcp 1.2.1/collections 3.2. It can also

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487488 ] Phil Steitz commented on DBCP-212: -- After running against instrumented dbcp and pool jars and different db engines, I

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487282 ] Phil Steitz commented on DBCP-212: -- Thanks. Also thanks in advance for running against pool 1.2/dbcp 1.2.1 to verify

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487235 ] Marcos Sanz commented on DBCP-212: -- Yes, the test has been made with Commons Pool 1.3 It is possible to determine tha

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487203 ] Phil Steitz commented on DBCP-212: -- Can you please provide a little more information on what exactly you are seeing -