PortUnificationServerHandler and Read/WriteTimeoutHandlers

["이희승 (Trustin Lee)"]

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.

HTH

fatzopilot wrote:
 > Hi Trustin,
 >
 >
 > Trustin Lee wrote:
 >> Perhaps you could insert the timeout handler *before* the port
 >> unification handler? Would it fix the problem?
 >>
 >
 > This saves the dummy handler, but the
 > org.jboss.netty.handler.timeout.ReadTimeoutException is still "thrown".
 > I additionally tried to just catch it and put it into the upstream in 
order
 > to be processed by some handler that implements execptionCaught. I.e. 
like
 > this:
 >
 > try {
 > pipeline.addLast("readTimeout", new ReadTimeoutHandler(new
 > HashedWheelTimer(), 1,TimeUnit.MINUTES));
 > pipeline.addLast("writeTimeout", new WriteTimeoutHandler(new
 > HashedWheelTimer(), 1,TimeUnit.MINUTES));
 > } catch (Exception e) {
 > Channels.fireExceptionCaught(ctx.getChannel(), e);
 > }
 > However, the exeption was not catched, so I presume it is not really 
thrown
 > but catched before and just printed. But I am unsure about this. I 
did not
 > experience "uncatchable" Exceptions before...
 >
 >
 >
 > --
 > View this message in context: 
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/PortUnificationServerHandler-and-Read-WriteTimeoutHandlers-tp6947674p6950052.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/20111031/f6314d4d/attachment.html