On Friday, June 20, 2003, at 11:41 AM, Michael Becke wrote:
Adrian,
I'm looking into to this and I agree it is quite strange. The part I don't understand is why the second attempt to write to the socket fails. The socket is not being closed on the HttpClient side until after the failure occurs. Any thoughts on how the connection is being closed?
Well I'm not really sure. It appears that the HttpConnection class thinks that it's still open but the underlying stream is actually closed. I'm just writing some tests to check this at the moment, but I believe it has to be the case because in HttpMethodBase.writeRequest at line 2179 we call conn.flushRequestStream which is what's causing the exception. However, immediately before that call if you add a debug statement to check if the connection is open, conn.isOpen() returns true.
Have you been able to independently reproduce this problem? I can reproduce it on 1.4.1 on OS X and Windows 2000 but it's possible I'm still screwing something up.
Mike
Adrian.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
