3
85%
trunk: 85%

Ran 24 Oct 2018 07:45PM UTC

Files 48

Run time 3s

Badge

Embed ▾

Committed 24 Oct 2018 07:30PM UTC coverage: 85.073% (+0.2%) from 84.922%

Job # 215.3

Build Type

Pull #11

travis-ci

Committed by

web-flow

Commit Message

POOL-356 fix deadlock on massive concurrent requests

Happens when blockWhenExhausted is active.
The idleObjects.takeFirst and .pollFirst operations perform a lock.
So if the pool is empty and the MaxTotal is hit we end up having multiple
Threads perform a lock internally via idleObjects.takeFirst().

But if a condition occurs to destroy the object instead of putting it back into the pool
then nobody notifies the Lock Condition.

The proposed solution will simply create a new object in that case and puts
it back into the idle queue IF there are active threads waiting for
some idle objects.

Pull Request Pull Request #11: POOL-356 add unit test for the deadlock

Run Details

2519 of 2961 relevant lines covered (85.07%)

85617.88 hits per line

apache / commons-pool / 215 / 3
85%
trunk: 85%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 215.3

apache / commons-pool / 215 / 3 85% trunk: 85%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 215.3

apache / commons-pool / 215 / 3
85%
trunk: 85%

README BADGES
x