简体繁体中英

Java Sockets: Socket.close() terminates connection different on Windows and Mac?

原文 2011-02-09 12:25:50 1 2 java/ macos/ sockets/ duplicates

Situation is as follows: I have a Java Application, that communicates over TCP to a Microcontroller with TCP Stack on it. The Stack on the Controller works fine, I can sort this out.

Problem is: When I terminate my connection to the Controller, I simply use socket.close() and the connection is terminated, no problem. On my Mac, this works too, but when I check Wireshark, there is the regular termination process [FIN,ACK] - [ACK] , but followed by a [TCP Dup ACK] Packet, that, so claimed by Wireshark, belongs to my [FIN,ACK] Packet. This only happens on a Mac and does not happen on a Windows machine on a VM on my mac or on my netbook...

Are there any tweaks I could use to not letting this Dup-ACK Packet to be transmitted? It actually jerks up the stack in the Controller by claiming that the closed session is still active and after 10 times connecting to the controller, the stack has no more space to accept new connections.

I'd be really thankful if someone could give me a hint!

2 answers

Well, if this is a problem in OS-provided TCP stack (which I believe it is) you may try to telnet from your mac to the device and close the connection. Just to see whether this dup ack would be still emitted. If it is, than swapping java versions/vendors (for example) won't do much good...

...oh, and maybe you'd be able to filter the offending packet with your firewall? That's a wild guess, as I actually know nothing about firewalling for MacOS...

I would actually recommend talking to the vendor of your MCU's tcp/ip stack.

While you might be able to tweak this one particular mac, you're going to have to get this fixed more permanently. And there's enough macs out there that you're going to have to deal with it sooner or latter.

Java/android socket.close() is not realized by server

Socket not closing serverside when calling socket.close() in client JAVA

Is Socket.close() considered a clean way to end the connection?

Anything I can do when socket.close() throws in Java?

Handling socket.close() gracefully

Socket not closing when calling socket.close()

About if(socket != null) socket.close();

Will socket.close() interrupt data transmission?

Multicast socket.close takes 3 minutes with TTL>1

Socket.close stuck for 15 minutes

暂无

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

Related Question Java/android socket.close() is not realized by server Socket not closing serverside when calling socket.close() in client JAVA Is Socket.close() considered a clean way to end the connection? Anything I can do when socket.close() throws in Java? Handling socket.close() gracefully Socket not closing when calling socket.close() About if(socket != null) socket.close(); Will socket.close() interrupt data transmission? Multicast socket.close takes 3 minutes with TTL>1 Socket.close stuck for 15 minutes

Related Tags

Java Sockets: Socket.close() terminates connection different on Windows and Mac?

Question

2 answers

solution1
1 2011-02-11 18:10:41

solution2
0 2011-02-10 13:27:57

Java Sockets: Socket.close() terminates connection different on Windows and Mac?

Question

2 answers

solution1 1 2011-02-11 18:10:41

solution2 0 2011-02-10 13:27:57

solution1
1 2011-02-11 18:10:41

solution2
0 2011-02-10 13:27:57