dev@glassfish.java.net

Re: intermittent deadlock in GF due to logging

From: Lloyd Chambers <Lloyd.Chambers_at_Sun.COM>
Date: Fri, 10 Apr 2009 10:02:05 -0700

Does this deadlock occur right away at startup? (not on VPN, so I
can't read the bug report right now).

Lloyd

On Apr 9, 2009, at 10:07 PM, Carla Mott wrote:

>
> Ok, I just wanted to verify that you were talking about the
> original deadlock you saw and not a new one.
>
> Thanks,
> Carla
>
> Richard S. Hall wrote:
>> On 4/10/09 12:42 AM, Carla Mott wrote:
>>> After updating your workspace you still see the deadlock? A
>>> workaround went in last night PST.
>> No, didn't mean to imply that. Just verifying that the original
>> deadlock did occur on a Mac too.
>> In truth, I have only ever seen the deadlock once, which is the
>> time I reported it to Sahoo last week or so.
>> -> richard
>>>
>>> Richard S. Hall wrote:
>>>> I do work on a Mac and I have seen it.
>>>>
>>>> -> richard
>>>>
>>>> On 4/9/09 1:39 PM, Carla Mott wrote:
>>>>> I will update the bug to contain this info. There is a problem
>>>>> still.
>>>>>
>>>>> The JDK version on the Mac doesn't contain this fix. I work on
>>>>> a Mac and haven't run into this issue but then I don't run the
>>>>> server like most folks so unless it happens at startup or during
>>>>> the quicklook test runs then I don't see it. Jerome checked in
>>>>> some code last night to work around this issue specifically to
>>>>> help the Mac users.
>>>>>
>>>>> Carla
>>>>>
>>>>> Sahoo wrote:
>>>>>> Carla,
>>>>>>
>>>>>> This is good finding. We should enforce this minimum JDK
>>>>>> version during server startup, because the deadlock appears
>>>>>> quite frequently. Can you address this as part of issue #7274?
>>>>>> Does anyone have any objections?
>>>>>>
>>>>>> Thanks,
>>>>>> Sahoo
>>>>>>
>>>>>> Carla Mott wrote:
>>>>>>>
>>>>>>> Several have reported intermittent hangs in GF lately that
>>>>>>> shows a deadlock in the logging code. After some
>>>>>>> investigation Dhiru found that there is a bug in the JDK and
>>>>>>> has been fixed. Please check the version of the JDK you are
>>>>>>> running and upgrade if needed.
>>>>>>>
>>>>>>> >Looks like this is caused by a JDK bug:
>>>>>>> >http://monaco.sfbay.sun.com/detail.jsf?cr=6487638
>>>>>>> >http://bugs.sun.com/view_bug.do?bug_id=6487638
>>>>>>>
>>>>>>> >This was fixed JDK 6u11. We were using JDK 6u6 on hudson.
>>>>>>>
>>>>>>> Carla
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>

Lloyd Chambers
lloyd.chambers_at_sun.com
GlassFish Team