[jira] [Closed] (POOL-189) close() does not release threads blocked on borrowObject()
[ https://issues.apache.org/jira/browse/POOL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz closed POOL-189. close() does not release threads blocked on borrowObject() -- Key: POOL-189 URL: https://issues.apache.org/jira/browse/POOL-189 Project: Commons Pool Issue Type: Bug Affects Versions: 1.5.6 Environment: java 1.6.0_24 Reporter: Adrian Nistor Fix For: 1.5.7 Attachments: BUG-189v1.diff, BUG-189v2.diff, Test.java Hi, When I call close() and borrowObject() concurrently with no objects in the pool, close() will finish but borrowObject() is blocked forever. The documentation of close() mentions that borrowObject() should fail with IllegalStateException, so I would expect the waiting threads to throw IllegalStateException. I will attach a test that exposes this problem. For this test, the expected output is: 0 1 2 ... 4999 DONE But when the bug manifests (almost always for this test), the output is: 0 1 2 The test does not finish, it just gets stuck after printing several values. Is this a bug or am I reading the documentation wrongly? Is there a patch for this? Thanks! Adrian -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (POOL-192) GenericKeyedObjectPool: clear() clears the keyed pool but does not decrease the item counter
[ https://issues.apache.org/jira/browse/POOL-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz closed POOL-192. GenericKeyedObjectPool: clear() clears the keyed pool but does not decrease the item counter Key: POOL-192 URL: https://issues.apache.org/jira/browse/POOL-192 Project: Commons Pool Issue Type: Bug Affects Versions: 1.5.6 Reporter: Helge Dannenberg Fix For: 1.5.7 If function 'clear(Object key)' in GenericKeyedObjectPool is called onto a keyed pool, the ObjectQueue (= the keyed pool) is removed from the pool list. Its items are deleteded in the function 'destroy()' afterwards. But as the ObjectQueue is already removed, the itemcounter _totalInternalProcessing is never decreased. As a result of this bug the pool exhausts even if the pool is empty. The solution is to decrease the counter _totalInternalProcessing in 'destroy()' also if ObjectQueue in null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DBCP-371) DelegatingDatabaseMetaData
[ https://issues.apache.org/jira/browse/DBCP-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz closed DBCP-371. Resolution: Duplicate Fix Version/s: (was: 1.2) 1.4.1 This duplicates DBCP-330, which has been fixed in the DBCP_1_4 branch. The fix will be included in DBCP 1.3.1 / 1.4.1 DelegatingDatabaseMetaData -- Key: DBCP-371 URL: https://issues.apache.org/jira/browse/DBCP-371 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.3, 1.4 Environment: Informix database Reporter: Fredrik Bertilsson Priority: Critical Fix For: 1.4.1 When calling Connection.getMetaData() new objects of DelegationDatabaseMetaData and corresponding vendor specific objects (like IfxDatabaseMetaData) are created and never released for garabage collection. This bug seem to have been introduced in version 1.3. Version 1.2 does not have this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DBCP-370) Please Release Commons Dbcp 1.4.1
[ https://issues.apache.org/jira/browse/DBCP-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz closed DBCP-370. Resolution: Invalid Please don't take this as a rude response, but this should be a comment for the dev list, not an issue. Thanks for the feedback / nudge. Please Release Commons Dbcp 1.4.1 - Key: DBCP-370 URL: https://issues.apache.org/jira/browse/DBCP-370 Project: Commons Dbcp Issue Type: Improvement Affects Versions: 1.4.1 Reporter: Yudhi Widyatama Labels: maven Bugs like DBCP-333 causes problem when creating a project using Maven. Without a commons-dbcp 1.4.1 release, artifacts that could be downloaded from Maven repository is limited to 1.4, which still have the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
