Read timeout errors in infinite loop

[Marc-André Laverdière]

I personally used my own timeout handler and its working fine. Maybe
there is a but in ReadTimeoutHandler?
Marc-André LAVERDIÈRE
"Perseverance must finish its work so that you may be mature and
complete, not lacking anything." -James 1:4
mlaverd.theunixplace.com/blog

 /"\
 \ /    ASCII Ribbon Campaign
  X      against HTML e-mail
 / \



2010/8/19 javadevmtl <java.dev.mtl at gmail.com>:
>
> So removing ReadTimeoutHandler completely from my application seems to work
> well. So far I have not been able to use ReadTimeoutHandler without issues.
> So either I'm using it wrong and don't understand it or it has issues.
>
> Simply put I want to make sure that if the client doesn't send the right
> amount of bytes/protocol, that the server can handle it. So far I sent 30
> requests to the server where the protocol is wrong and I can see in
> JVisualVM that the 8 worker threads are running 100% of the time but cpu
> looks ok.
>
> Client hasn't timed out yet. Is that because I have keepalive set on the
> server?
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Read-timeout-errors-in-infinite-loop-tp5440336p5441486.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
>