Deadlock encountered.

[Virat Gohil]

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