<p>I think you need to put the handler that guarantees ordering of events.</p>
<p><blockquote type="cite">On 3 Nov 2010 03:59, "Bill Brochuwski" <<a href="mailto:bbrochu@sympatico.ca">bbrochu@sympatico.ca</a>> wrote:<br><br><br>
Hi,<br>
<br>
When my pipeline does not contain an ExecutionHandler, the server is<br>
notified immediately<br>
when a client disconnects. If I add an ExecutionHandler to my pipeline, the<br>
server becomes<br>
aware of the client disconnection only when it tries to write to it.<br>
<br>
// Only one instance created<br>
ExecutionHandler executionHandler =<br>
new ExecutionHandler(new OrderedMemoryAwareThreadPoolExecutor(16,<br>
512*1024, 1024*1024));<br>
<br>
<br>
in MyChannelPipelineFactory.getPipeline():<br>
<br>
// If I comment out the following line, the server gets notified<br>
immediately of a client<br>
// disconnect (exceptionCaught in MySimpleChannelUpstreamHandler)<br>
pipeline.addLast("executionHandler", executionHandler); // Must be shared<br>
among all channels.<br>
<br>
pipeline.addLast("businessLogicHandler", new<br>
MySimpleChannelUpstreamHandler());<br>
<br>
Thanks<br>
<font color="#888888">--<br>
View this message in context: <a href="http://netty-forums-and-mailing-lists.685743.n2.nabble.com/ExecutionHandler-in-pipeline-does-not-forward-client-disconnected-event-tp5699388p5699388.html" target="_blank">http://netty-forums-and-mailing-lists.685743.n2.nabble.com/ExecutionHandler-in-pipeline-does-not-forward-client-disconnected-event-tp5699388p5699388.html</a><br>
Sent from the Netty User Group mailing list archive at Nabble.com.<br>
_______________________________________________<br>
netty-users mailing list<br>
<a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
</font></blockquote></p>