Are Java Socket shutdownOutput and shutdownInput responsible for "Duplicate ACK #: 1" -
at first, sorry long explanation of below issue.
i have simple tcp client. here code snippet:
...... ouputstream = socket.getoutputstream(); . ..... bufferedoutputstream.flush(); socket.shutdownoutput(); ...... inputstream = socket.getinputstream(); ..... while(r=bufferedreader.read()!-1){ reading response } socket.shutdowninput(); ....... socket.close();
my tcp client works multiple tcp servers except 1 particular tcp server. tcp client not response server in morning , afternoon (server pick hour time) response without problem in evening, night , morning.
therefore, have used wireshark inspect packet of network during server pick hour time.
the inspection snippet of wireshark in pick hour:
4 0.072547 ccc.ccc.ccc.ccc sss.sss.sss.sss tcp 66 clientport > serverport [fin, ack] seq=2008 ack=1 win=14720 len=0 tsval=992536 tsecr=4189227564 .... .... 7 0.156504 sss.sss.sss.sss ccc.ccc.ccc.ccc tcp 66 serverport > clientport [ack] seq=1 ack=1449 win=8704 len=0 tsval=332931140 tsecr=259206577 8 0.159312 sss.sss.sss.sss ccc.ccc.ccc.ccc tcp 78 [tcp dup ack 7#1] serverport > clientport [ack] seq=1 ack=1449 win=8704 len=0 tsval=332931141 tsecr=259206577 sle=2008 sre=2009 [seq/ack analysis] [tcp analysis flags] [this tcp duplicate ack] [duplicate ack #: 1] [duplicate ack in frame: 7] [expert info (note/sequence): duplicate ack (#1)] [message: duplicate ack (#1)] [severity level: note] [group: sequence] note: sss.sss.sss.sss server ip , ccc.ccc.ccc.ccc client ip
- is problem of tcp server? or socket.shutdownoutput() , socket.shutdowninput() responsible duplicate ack?
i not sure problem because other server ok tcp client (with shutdownouput , shutdowninput) , particular server not responding during pick hour (morning , afternoon) time working other time.
i glad, if kindly suggests me issue.
is problem of tcp server?
the problem intervening network dropping packets.
are socket.shutdownoutput() , socket.shutdowninput() responsible duplicate ack?
no.
Comments
Post a Comment