[#POOL-144] Maxwait exceeded causes pool capacity leak

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
	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:

Repository	Revision	Date	User	Message
ASF	#784440	Sat Jun 13 17:41:00 UTC 2009	markt	Add a test case for ~~POOL-144~~. Patch by Phil Steitz.
				Files Changed
				MODIFY /commons/proper/pool/trunk/src/test/org/apache/commons/pool/impl/TestGenericObjectPool.java

Repository	Revision	Date	User	Message
ASF	#784441	Sat Jun 13 17:42:28 UTC 2009	markt	Fix ~~POOL-144~~ and related issues for GOP and GKOP.
				Files Changed
				MODIFY /commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericKeyedObjectPool.java MODIFY /commons/proper/pool/trunk/src/java/org/apache/commons/pool/impl/GenericObjectPool.java