Are Java Socket shutdownOutput and shutdownInput responsible for "Duplicate ACK #: 1" -

First of all, I apologize for the long explanation of the issue.

I have a simple TCP client. Here is the code snippet:

  ...... ouputStream = socket.getOutputStream (); . ..... bufferedOutputStream.flush (); Socket.shutdownOutput (); ...... InputStream = socket.getInputStream (); ..... while (r = bufferedReader.read ()! - 1) {feedback read} socket.shutdownInput (); ....... socket.close ();  

My TCP client works with many TCP servers except for a particular TCP server, my TCP customer receives no response from that server in the morning and afternoon (server takes time) , But in the evening, at night, and in the morning in the morning, without any problem, fully reacted.

Therefore, I have the wireshark to monitor the network packets during the time of server time.

Wireless inspection snippet in hours:

Serverport [FIN, ACK] Seq = 2008 ACC = 1 Win = 14720 Lane = TSWAL = 992536 TSACR = 4189227564 .... .... 7 0.156504 SSS.SSSSS Ss CCC. CCC. CCCCCCC TCP 66 Serverport> Clientport [ACK] CEC = 1 ACC = 1449 Win = 8704 Lane = 0 TSWL = 332931140 TSACR = 259206577 8 0.159312 SSS.ssssssssssssss CCC CCC. CCC. CCC TCP 78 [TCP Dup ACK 7 # 1] Serverport> Customers [ACK] CEC = 1 ACC = 1449 Win = 8704 Lane = 0 TSWL = 332931141 TSECR = 25 9 206577 SLE = 2008 SRE = 200 9 [SEC / ACK Analysis] [TCP analysis flag] [This is a TCP duplicate ACC] [Duplicate ACK #: 1] [Series Level: Attention] [Group: Sequence] Note: [ACK (ACK)] [Note: Duplicate ACK (# 1)] [Message: Duplicate ACK (Note 1) SSS.SSS.SSS.SSS iS Server IP and CCCCCC. CCC. CCC is Customer IP

• Is this TCP server the problem? Or socket Shutdownoptip () and socket.shutdownInput () are responsible for duplicate ACK?

I'm not sure where the problem is because the other server is fine with my TCP client (shutdownApot and shutdownpoint) and that particular server will not respond only during pickup hours (morning and afternoon) Is giving, but is working at other times.

I would be glad if someone gave me suggestions about this issue.

Is this TCP server problem?

The problem is probably with interval network droping packets.

socket.shutdownOutput () and Socket Duplicate ACK?

No

is responsible for .shutdownInput () what?