Thanks Oleg for your reply. The Wireshark trace shows clearly that data was coming in chunks/frames and also got assembled finally with HTTP headers. Can JRE close the socket on its own when it receives TCP Flags [FIN, PSH, ACK] in the frame without the caller closing the socket?
Is there any other solution other than trying with different JDK versions? Regards Vasu On 25 August 2017 at 19:05, Oleg Kalnichevski <[email protected]> wrote: > On Fri, 2017-08-25 at 17:58 +0530, Vasudevan Comandur wrote: > > Hi Oleg, > > > > Thanks for your reply. When I had a look at the wireshark trace, I > > saw > > that server was sending the data > > in chunks and all the chunks were assembled finally with HTTP > > headers. > > The TCP flags had [FIN, PSH, ACK] > > set for the HTTP protocol and the data was also there. The retry > > happend > > 4 times and the data was coming > > all the tme from the server with same TCP flags settings. > > > > I saw TCP packet from client with [ACK] flag followed by another > > TCP > > packet with [RST, ACK] flags. > > But the app did not receive the message. > > > > I am running JDK 1.8.0.102 and OS is windows 8. > > > > I can share the wireshark log trace if you need. > > > > By changing the java version, will it help to solve the issue. > > > > Looking forward to your suggestion. > > > > Thanks & Regards > > Vasu > > > > Maybe the server sent a response, maybe it did not. What looks pretty > clear to me is that the JRE believes the socket was closed by an > opposite endpoint without returning any data. > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
