> I run into 2 small bugs - the diff solves the problem for me, > maybe for others :-) > > First, on some VMs the SocketRR will hung for a very long time. > That's because even if close() is called on the socket, the > read() will remain blocked. Adding a soTimeout and > checking for done solves this. > > The other - with some servers, if available() returns > 0 we read a single byte, and then send it. Then we'll > send a second packet with the rest of the request. > That will confuse at least apache  (who would see > OST instead of POST - still trying to figure out why ). > I see no reason to read a single byte - we'll block > anyway.
> I run into 2 small bugs - the diff solves the problem for me,
> maybe for others :-)
>
> First, on some VMs the SocketRR will hung for a very long time.
> That's because even if close() is called on the socket, the
> read() will remain blocked. Adding a soTimeout and
> checking for done solves this.
>
> The other - with some servers, if available() returns
> 0 we read a single byte, and then send it. Then we'll
> send a second packet with the rest of the request.
> That will confuse at least apache  (who would see
> OST instead of POST - still trying to figure out why ).
> I see no reason to read a single byte - we'll block
> anyway.

Submitted by Costin Manolache


git-svn-id: 8699849808240b02471d01f5aaa03ec0c1cb68ee@246602 13f79535-47bb-0310-9956-ffa450edef68

apache/axis1-java,apache/axis1-java,apache/axis1-java,apache/axis1-java