Deadlock encountered.

[Virat Gohil]

Virat Gohil-3 wrote:
> 
> Hi All,
> 
> During our testing we found that sometimes the threadtump identifies the
> following deadlock:
> 
> Found one Java-level deadlock:
> =============================
> "pool-3-thread-16":
>   waiting to lock monitor 0x00124468 (object 0xc15d65e0, a
> java.lang.Object),
>   which is held by "New I/O server worker #1-2"
> "New I/O server worker #1-2":
>   waiting to lock monitor 0x00124348 (object 0xc15d6610, a
> java.util.LinkedList),
>   which is held by "pool-3-thread-16"
> 
> Java stack information for the threads listed above:
> ===================================================
> 
> "pool-3-thread-16":
>     at org.jboss.netty.handler.ssl.SslHandler.wrap(SslHandler.java:477)
>     - waiting to lock <0xc15d65e0> (a java.lang.Object)
>     - locked <0xc15d6610> (a java.util.LinkedList)
>     at
> org.jboss.netty.handler.ssl.SslHandler.handleDownstream(SslHandler.java:353)
>     at
> org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:590)
> </SNIP>
> 
> "New I/O server worker #1-2":
>     at org.jboss.netty.handler.ssl.SslHandler.wrap(SslHandler.java:468)
>     - waiting to lock <0xc15d6610> (a java.util.LinkedList)
>     at org.jboss.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:733)
>     at org.jboss.netty.handler.ssl.SslHandler.decode(SslHandler.java:445)
>     at
> org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:270)
>     at
> org.jboss.netty.handler.codec.frame.FrameDecoder.cleanup(FrameDecoder.java:320)
>     at
> org.jboss.netty.handler.codec.frame.FrameDecoder.channelDisconnected(FrameDecoder.java:220)
>     at
> org.jboss.netty.handler.ssl.SslHandler.channelDisconnected(SslHandler.java:369)
>     at
> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:119)
> </SNIP>
> 
> Some more information:
> 1. JDK Version: 1.5
> 2. OS: Sun Solaris 10.
> 3. Netty version: 3.1.0Beta2
> 
> Any pointers on how to avoid these deadlocks?
> 
> Thanks,
> 
> Virat
> 

Hi Trustin,

I recently updated to Netty 3.1 CR1 build. I seem to have struck a similar
defect. I am attaching the thread dump along with this email. 

Kindly let me know if you need any further information. 

Thanks,

Virat
http://n2.nabble.com/file/n3172958/deadlocks.zip deadlocks.zip 


-- 
View this message in context: http://n2.nabble.com/Deadlock-encountered.-tp2868711p3172958.html
Sent from the Netty User Group mailing list archive at Nabble.com.