Jorge,
Could you please test the patch attached to
http://issues.apache.org/bugzilla/show_bug.cgi?id=33947
which is against the 2.02 code base. Please give feedback if it solves your problem.
TIA
Ortwin Gl�ck
Jorge Gonzalez Varela wrote:
After doing some tests using HttpClient source code, I have found that Socket#getReceiveBufferSize() method returned a zero value. This is a random behaviour because it usually returns 8192 bytes. When zero is returned, the exception is thrown and HttpClient fails.
I have trying to isolate different parts and I have found that under some circumstances, Socket#getReceiveBufferSize() returns 0. I have developed a very simple multi-threading application that starts threads and waits until they die. Each thread open a Socket to a WebServer and invokes Socket#getReceiveBufferSize(). Sometimes, this method returns 0 for some sockets.
I have tried with different JVM versions under Windows XP-Service Pack 2:
a) java version "1.3.1_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode)
b) java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode)
So, it doesn't seem like a JVM bug. It seems like a Windows bug/"feature".
What solution do you recommend me to patch HttpConnection?
Kind regards,
Jorge.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
