> Changing HTTP keep alive does not change anything....
So you still see broken pipe exception, right?
> I have seen there is a bug GRIZZLY-959 about keepalive when acceptor thread
> is greater than 1...
>
> I have patched my glassfish v2 with grizzly 1.0.39 by changing the prefix
> classpath. I took the file from grizzly repo
> (http://download.java.net/maven/2/com/sun/grizzly/grizzly-framework-http/1.0.39/).
Right, it's what you told in the 1st post, so it shouldn't be the case.
> I will try to increase socket buffer. Do you think it can help ?
From what you're reporting, it looks like bottleneck occurs when server
writes response to client, which should mean client is not able to
process server response as fast as server sends it.
If that's the case - you can try to increase server write timeout i
mentioned in prev. post.
The increasing of socket buffer may help to delay the problem, but not
sure if it would resolve it. Depends on your concrete usecase.
WBR,
Alexey.
>
>
>
> --
> View this message in context: http://grizzly.1045725.n5.nabble.com/Broken-Pipe-and-client-is-busy-or-timeout-errors-tp4268012p4268940.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.