hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <asan...@wso2.com>
Subject Re: Can an HTTP server close the socket before its client has finished receiving the message?
Date Tue, 15 Jul 2008 16:25:14 GMT
Hi Oleg, Ortwin and Mike

Sorry for my delay in responding,.. I am unable to find out the version 
of Weblogic, but will try to find that out. I will also try to get a 
tcpdump or a wireshark dump to investigate this further and share that 
with you. I am accessing this service histed in Europe, over a VPN from 
Sri Lanka, but I guess that will [hopefully] not spoil a tcpdump or 
wireshark dump.. Also this service is available only over https, so I am 
unable to say of this is specific to https, but will try to find more 
details and update you

many thanks
>> The exact timing of the remote side closing the connection shouldn't matter. If 
>> coded propertly, buffers are flushed before/on close. The TCP FIN sequence will 
>> be queued *after* all the data packets. So the data will remain within the TCP 
>> stack and is not lost, even if the client starts reading long after the 
>> connection has been closed. A packet dump (Wireshark) should give us more 
>> information here.
>> Ortwin
> ´╗┐Asankha,
> The most plausible cause of this problem is a failure to flush the
> output buffer on the server side. Given this is Weblogic, which is known
> to be very stable, I admit this assumption does seem far fetched. So, I
> would not rule out HttpCore SSL session behaving funny for some reason. 
> What version of Weblogic is it? Is it fully patched?
> Please let me know if I can help you in any way.
> Oleg 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message