<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>I'm not sure this is directly relevant, but you have to share a HashedWheelTimer instance among all connections because creating a single timer instance will also create a single Thread instance. Please refer to the JavaDoc of HashedWheelTimer, fix the code, and let me know your observation.<BR>
<BR>
HTH<BR>
<BR>
fatzopilot wrote:<BR>
> Hi Trustin,<BR>
><BR>
><BR>
> Trustin Lee wrote:<BR>
>> Perhaps you could insert the timeout handler *before* the port<BR>
>> unification handler? Would it fix the problem?<BR>
>><BR>
><BR>
> This saves the dummy handler, but the<BR>
> org.jboss.netty.handler.timeout.ReadTimeoutException is still "thrown".<BR>
> I additionally tried to just catch it and put it into the upstream in order<BR>
> to be processed by some handler that implements execptionCaught. I.e. like<BR>
> this:<BR>
><BR>
> try {<BR>
> pipeline.addLast("readTimeout", new ReadTimeoutHandler(new<BR>
> HashedWheelTimer(), 1,TimeUnit.MINUTES));<BR>
> pipeline.addLast("writeTimeout", new WriteTimeoutHandler(new<BR>
> HashedWheelTimer(), 1,TimeUnit.MINUTES));<BR>
> } catch (Exception e) {<BR>
> Channels.fireExceptionCaught(ctx.getChannel(), e);<BR>
> }<BR>
> However, the exeption was not catched, so I presume it is not really thrown<BR>
> but catched before and just printed. But I am unsure about this. I did not<BR>
> experience "uncatchable" Exceptions before...<BR>
><BR>
><BR>
><BR>
> --<BR>
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/PortUnificationServerHandler-and-Read-WriteTimeoutHandlers-tp6947674p6950052.html<BR>
> Sent from the Netty User Group mailing list archive at Nabble.com.<BR>
> _______________________________________________<BR>
> netty-users mailing list<BR>
> netty-users@lists.jboss.org<BR>
> https://lists.jboss.org/mailman/listinfo/netty-users</BODY></HTML>