Tasks added to OrderedMemoryAwareThreadPoolExecutor may be lost. #234

Closed
zhmt opened this Issue Mar 15, 2012 · 2 comments

Projects

None yet

2 participants

@zhmt
zhmt commented Mar 15, 2012

Tasks added to ChildExecutor after the "for(;;) " terminated and before "isRunning.set(false)", will be lost silently.
I have post a detailed descrition on stackoverflow:

http://stackoverflow.com/questions/9697371/the-netty-server-seems-to-be-blocked-when-i-add-a-executionhandler/9716056#9716056

@normanmaurer normanmaurer was assigned Mar 15, 2012
@normanmaurer
Member

Let me fix it today..

@normanmaurer
Member

Fixed.. Thanks for the detailed explaintation and the patch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment