[POOL-180] Max active per key can be exceeded by one

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5
• Fix Version/s: 1.5.6
• Assignee: Mark Thomas
• Reporter: Phil Steitz
• Created: 05/Jan/11 02:15
• Updated: 08/Apr/11 13:54
• Resolved: 24/Mar/11 11:32

Description

When instances in the pool fail validation with high frequency, maxTotal is less than maxActive times the number of keys, and destroy has latency, the maxActive contract can be violated (i.e., the number of instances created under a given key minus the number destroyed can exceed maxActive).

Attaching a test case that fails against POOL_1_X