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

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz reopened DBCP-212: -- Not really fixed. As Phil wrote: "until pool is improved somehow to be more intelligent about destroying idl

[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: (POOL-93) Reduce contention by making borrow & return more independent from each other

[ https://issues.apache.org/jira/browse/POOL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490928 ] Marcos Sanz commented on POOL-93: - I have included a simmilar patch to Holger's, this time for the GenericObjectPool.

[jira] Updated: (POOL-93) Reduce contention by making borrow & return more independent from each other

[ https://issues.apache.org/jira/browse/POOL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated POOL-93: Attachment: perf-patch-GenericPool.txt GenericObjectPool.patch Patch for GenericPool and perfo

[jira] Updated: (DBCP-216) Improvement of error recovery in KeyedCPDSConnectionFactory

[ https://issues.apache.org/jira/browse/DBCP-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated DBCP-216: - Attachment: KeyedCPDSConnectionFactory.java.diff > Improvement of error recovery in KeyedCPDSConnectionFact

[jira] Created: (DBCP-216) Improvement of error recovery in KeyedCPDSConnectionFactory

Improvement of error recovery in KeyedCPDSConnectionFactory --- Key: DBCP-216 URL: https://issues.apache.org/jira/browse/DBCP-216 Project: Commons Dbcp Issue Type: Improvement Affec

[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] Updated: (POOL-101) BaseObjectPool does not provide atomicity for closed-Operations

[ https://issues.apache.org/jira/browse/POOL-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated POOL-101: - Description: Though the "closed" field has been declared volatile in the abstract class BaseObjectPool, at

[jira] Created: (POOL-101) BaseObjectPool does not provide atomicity for closed-Operations

BaseObjectPool does not provide atomicity for closed-Operations --- Key: POOL-101 URL: https://issues.apache.org/jira/browse/POOL-101 Project: Commons Pool Issue Type: Bug Affec

[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] Updated: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated DBCP-212: - Attachment: output.txt > PoolingDataSource closes physical connections > --

[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] Updated: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated DBCP-212: - Attachment: DBCPtester.java New file with additional debugging that actually causes the bug. > PoolingData

[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_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] Updated: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated DBCP-212: - Environment: Windows XP, Java 1.5.0_06-b05, Sybase ASE 12.5.4, jConnect 6.0.5 EBF 13862, Commons Pool 1.3

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

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanz updated DBCP-212: - Attachment: DBCPtester.java Execution of the programm does NOT produce any exception, error or relevant ou

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

PoolingDataSource closes physical connections - Key: DBCP-212 URL: https://issues.apache.org/jira/browse/DBCP-212 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2.2 Environm