ExecutionHandler in pipeline does not forward client disconnected event

[Marc-André Laverdière]

I think you need to put the handler that guarantees ordering of events.

On 3 Nov 2010 03:59, "Bill Brochuwski" <bbrochu at sympatico.ca> wrote:


Hi,

When my pipeline does not contain an ExecutionHandler, the server is
notified immediately
when a client disconnects. If I add an ExecutionHandler to my pipeline, the
server becomes
aware of the client disconnection only when it tries to write to it.

 // Only one instance created
 ExecutionHandler executionHandler =
    new ExecutionHandler(new OrderedMemoryAwareThreadPoolExecutor(16,
512*1024, 1024*1024));


in MyChannelPipelineFactory.getPipeline():

 // If I comment out the following line, the server gets notified
immediately of a client
 // disconnect (exceptionCaught in MySimpleChannelUpstreamHandler)
 pipeline.addLast("executionHandler", executionHandler); // Must be shared
among all channels.

 pipeline.addLast("businessLogicHandler", new
MySimpleChannelUpstreamHandler());

Thanks
--
View this message in context:
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/ExecutionHandler-in-pipeline-does-not-forward-client-disconnected-event-tp5699388p5699388.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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20101104/f7fb8b82/attachment.html