Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Asankha C. Perera
Hi All When talking over SSL to a BEA WLI server, it responds with a "Connection: close" header, and seems to close the socket, before Apache Synapse (using HttpCore/NIO) could read the full message (~11K in size). Its setting the 'Content-length' header, but when debugging the SSL communicat

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Ortwin Glück
Asanka, 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 start

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Oleg Kalnichevski
On Fri, 2008-07-11 at 12:43 +0200, Ortwin Glück wrote: > Asanka, > > 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

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Ortwin Glück
Oleg Kalnichevski wrote: 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

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Oleg Kalnichevski
On Fri, 2008-07-11 at 19:19 +0200, Ortwin Glück wrote: > > Oleg Kalnichevski wrote: > > 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 fetch

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Ortwin Glück
Oleg Kalnichevski wrote: On Fri, 2008-07-11 at 19:19 +0200, Ortwin Glück wrote: Oleg Kalnichevski wrote: 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

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-11 Thread Mike Dillon
begin Oleg Kalnichevski quotation: > On Fri, 2008-07-11 at 19:19 +0200, Ortwin Glück wrote: > > > > Oleg Kalnichevski wrote: > > > 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 stab

Re: Can an HTTP server close the socket before its client has finished receiving the message?

2008-07-15 Thread Asankha C. Perera
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, o