users@grizzly.java.net

Re: "Broken Pipe" and "client is busy or timeout" errors

From: wild <itchy75_at_hotmail.fr>
Date: Tue, 29 Mar 2011 00:40:42 -0700 (PDT)

Changing HTTP keep alive does not change anything....

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/).

I will try to increase socket buffer. Do you think it can help ?


         

--
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.