Yes I still have broken pipe exceptions... I have read that 5 minutes is the
maximum keep alive timeout so i didn't increase it more than 5 minutes.
For the "client too busy" exception :
My problem is that we send a lot of "message" to the client connection, and
one after another.
The sequence is
while(stillMessageToSend or max message limit not reached) {
response.write(message);
response.flush();
}
So If a increase the server timeout, i will keep a thread to many times and
enqueue too many messages. If the client is too slow to read messages, then
i think the only solution is ti reduce the number of messages send.
I will try to increase it but we need to send fast.....
--
View this message in context: http://grizzly.1045725.n5.nabble.com/Broken-Pipe-and-client-is-busy-or-timeout-errors-tp4268012p4270285.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.