Issue Details (XML | Word | Printable)

Key: POOL-144
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Phil Steitz
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Commons Pool

Maxwait exceeded causes pool capacity leak

Created: 12/Jun/09 11:03 PM   Updated: 19/Jun/09 04:06 PM
Return to search
Component/s: None
Affects Version/s: 1.5
Fix Version/s: 1.5.1

Time Tracking:
Not Specified

File Attachments:
  File Name Date Attached Attached By Size
Text File Licensed for inclusion in ASF works latch_leak.patch 2009-06-12 11:04 PM Phil Steitz 2 kB

Resolution Date: 13/Jun/09 05:43 PM


 Description  « Hide
When exhausted action is set to WHEN_EXHAUSTED_BLOCK, maxwait is positive and client threads time out waiting for idle objects, capacity can be "leaked" from GenericObjectPools and GeneritCkeyedObjectPools.

Test case and patch for GOP attached.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Phil Steitz made changes - 12/Jun/09 11:04 PM
Field Original Value New Value
Attachment latch_leak.patch [ 12410521 ]
Phil Steitz made changes - 12/Jun/09 11:45 PM
Fix Version/s 1.5.1 [ 12314030 ]
Mark Thomas made changes - 13/Jun/09 05:43 PM
Resolution Fixed [ 1 ]
Status Open [ 1 ] Resolved [ 5 ]
Phil Steitz made changes - 19/Jun/09 04:06 PM
Status Resolved [ 5 ] Closed [ 6 ]

Powered by a free Atlassian JIRA open source license for Apache Software Foundation. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators