On 05/09/2013 10:35 AM, Peter Levart wrote:
In my experience, the thread dies between 10-20ms after interrupting, so waiting for about 500ms is enough I think.
But only if the test is started with low max. heap setting. When trying with large heaps (2G+), a long GC pause can ruin Thread.sleep() enforced ordering. The test also works with heaps as low as 16m, so perhaps it should be started with -Xmx64m or even -Xmx32m...
Regards, Peter
