NioWorker unexpected exception in selector loop.

["이희승 (Trustin Lee)"]

Hi,

I took a look into this issue, but I don't have much clue at the moment.

Logically, currentWriteBuffer is always non-null if currentWriteEvent is 
non-null.  If currentWriteEvent is null, a new event if fetched into it 
and currentWriteBuffer is assigned with a new buffer.

Could you post a simple application that reproduces the problem?

Thanks,
Trustin


On 05/19/2011 11:06 PM, beric wrote:
> OK after more refactoring I'm still out of luck.
> Can you please give me a hint?
>
>
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/NioWorker-unexpected-exception-in-selector-loop-tp6365771p6382090.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users


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