Deadlock encountered.

[Trustin Lee]

Thanks to the full thread dump, I think I have found the cause of the
dead lock.  The two dead locks you pasted were caused by the same bug.
 The revision of the fix is 1282.  Build from the trunk or grab a
nightly build in a couple hours, and let me know if my fix works for
you.

It is pretty difficult to avoid a dead lock once a SSLEngine is used
in a multi-threaded environment, so I hope you understand this sort of
issue. :)

— Trustin Lee, http://gleamynode.net/



On Tue, May 12, 2009 at 11:13 PM, Virat Gohil <virat4lug at gmail.com> wrote:
> Hi Trustin,
>
> The following is the dump for the deadlock I reported in my first mail:
>
> http://pastebin.com/f3a9c8d0d
>
> We also saw the a similar deadlock and the following might also be helpful:
>
> http://pastebin.com/fa02e012
>
> Please let me know if you would like me to investigate some more :)
>
> Thanks,
>
> Virat
>
> I will either find a way or make one.
> Sent from Bangalore, KA, India
>
>
> On Tue, May 12, 2009 at 7:22 PM, Trustin Lee <tlee at redhat.com> wrote:
>>
>> On Tue, May 12, 2009 at 10:43 PM, Trustin Lee <tlee at redhat.com> wrote:
>> > Thanks for posting the bug first of all.  It is a dead lock indeed. :-(
>> >
>> > Could you post the full stack trace of the "New I/O server worker
>> > #1-2" thread?  You stripped out the information where exactly the lock
>> > '0xc15d6610' was acquired.
>>
>> I meant '0xc15d65e0' actually.
>>
>> — Trustin Lee, http://gleamynode.net/
>>
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>