RFR (XXS) 8069068: VM warning: WaitForMultipleObjects timed out (0) ...

Ivan Gerasimov ivan.gerasimov at oracle.com
Wed May 20 16:00:54 UTC 2015



On 20.05.2015 18:19, Daniel D. Daugherty wrote:
> On 5/20/15 7:57 AM, Ivan Gerasimov wrote:
>>
>>
>> On 20.05.2015 10:04, David Holmes wrote:
>>> Hi Ivan,
>>>
>>> On 20/05/2015 9:54 AM, Ivan Gerasimov wrote:
>>>> Hello!
>>>>
>>>> Since the beginning of the year a warning about an expired timeout has
>>>> been seen a few times.
>>>> It is most likely to observe this under a heavy load, when many 
>>>> threads
>>>> are exiting.
>>>>
>>>> The propose is to increase the timeout.
>>>> The rationale is that if an application needs more time for the 
>>>> threads
>>>> to exit, let's give it that time.
>>>
>>> Rather than just bumping the timeout a little I would suggest 
>>> bumping it a lot - make it a few minutes. If that fails then it 
>>> suggests we have a real problem not just a slow or loaded machine. 
>>> Otherwise if we just keep bumping the timeout it serves no purpose.
>>>
>>
>> Alright. Then let's make it 5 minutes for both product and debug bits:
>>
>> WEBREV: http://cr.openjdk.java.net/~igerasim/8069068/01/webrev/
>
> Thumbs up. If I remember correctly, we'll only hit the
> 5 minute timeout if we end up with the bottleneck where
> too many threads are queued up to leave... and none of
> the threads that are leaving make progress...
>
Yes. That's correct.
Thank you Dan.

Sincerely yours,
Ivan

> Dan
>
>
>>
>> Sincerely yours,
>> Ivn
>>
>>
>>> Cheers,
>>> David
>>>
>>>
>>>> BUGURL: https://bugs.openjdk.java.net/browse/JDK-8069068
>>>> WEBREV: http://cr.openjdk.java.net/~igerasim/8069068/00/webrev/
>>>>
>>>> Sincerely yours,
>>>> Ivan
>>>
>>>
>>
>
>
>



More information about the hotspot-runtime-dev mailing list