ok I will try to increase the timeout.... This change should fix the 2 errors
("Broken Pipe" or "client is busy or timeout") or only one ? Can you explain
why it should help ?
if channel.write send the data, why do we have to call selector.select() ?
After som check on client side, it seams that the connection is still alive
but selector.select() is returning 0.
it is difficult to provide a test case because it happened sometimes, mainly
when the load increase. Our use of comet is simple, we have implemented a
comet handler inspired from ConcurrentCometHandler and we write in the
httpResponse each time we have to write an event.
We implement our own thread pool in order to handler priority and use
several comet context in the same comet engine.
thanks
william
--
View this message in context: http://grizzly.1045725.n5.nabble.com/Broken-Pipe-and-client-is-busy-or-timeout-errors-tp4268012p4268394.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.