The change in r1174432 stopped tests from hanging, but the fix there
was for a different liveness problem. I just committed a test,
testLivenessPerKey that provides a simple example of what can go
wrong. It also shows that approach 0) below will not work (because
clearOldest is called on borrow/c
I am pretty sure that the analysis above is correct. We need a way
to either wake up the waiting threads and allow them to create when
there is total capacity or push instances to the queues they are
waiting on. This is less of a problem for GOP, because invalidate
is the only way it can happen;
On 9/11/11 1:49 PM, Phil Steitz wrote:
> I don't understand why exactly, but testMaxActivePerKeyExceeded is
> now hanging regularly for me using 1.6.0_26 (Apple Lion). In the
> thread dump, I get the driving test thread:
>
> "main" prio=5 tid=7feb5b001800 nid=0x1057f1000 waiting on condition
> [10
I don't understand why exactly, but testMaxActivePerKeyExceeded is
now hanging regularly for me using 1.6.0_26 (Apple Lion). In the
thread dump, I get the driving test thread:
"main" prio=5 tid=7feb5b001800 nid=0x1057f1000 waiting on condition
[1057ee000]
java.lang.Thread.State: TIMED_WAITING
