简体繁体中英

Multicast socket.close takes 3 minutes with TTL>1

原文 2012-04-19 13:34:14 9 2 java/ .net/ sockets/ multicast

On certain Windows machines, I'm seeing a multicast socket.close call take ~3 minutes.

This is reproducible in both Java and .NET across various different kinds of NICs and Windows flavors.

It's not reproducible on most machines, but the ones that have it seem to follow the same pattern. A TTL>1 causes the 3 minute socket.close and any TTL==1 seems to close the socket almost instantly.

My questions are is anyone else seeing this issue and does anyone know why it's happening?

2 answers

I think I've solved the mystery of Socket.Close() taking 3 minutes to complete when using a multicast TTL>1: It occurs every time the routing and RAS service (RRAS) has been started. This KB entry explains it and gives a hotfix: http://support.microsoft.com/kb/2555948/en-us

Using netsh interface ipv4 set global multicastforwarding=disabled in an admin shell brings Socket.Close() time back to normal.

Yeah, I can confirm this. Same behavior in C++ on Windows 7 on UDP sockets. I've discovered that not joining the same multicast group you are sending to solves the problem on my project.

Socket.close stuck for 15 minutes

Handling socket.close() gracefully

Socket not closing when calling socket.close()

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

Will socket.close() interrupt data transmission?

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

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

Socket.close() have no effect during Socket.connect()

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

Android socket.close() causes “the system call was canceled”?

暂无

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 Socket.close stuck for 15 minutes Handling socket.close() gracefully Socket not closing when calling socket.close() About if(socket != null) socket.close(); Will socket.close() interrupt data transmission? Java/android socket.close() is not realized by server Socket not closing serverside when calling socket.close() in client JAVA Socket.close() have no effect during Socket.connect() Is Socket.close() considered a clean way to end the connection? Android socket.close() causes “the system call was canceled”?

Related Tags

Multicast socket.close takes 3 minutes with TTL>1

Question

2 answers

solution1
2 2013-12-20 13:29:53

solution2
1 2012-08-01 10:54:38

Multicast socket.close takes 3 minutes with TTL>1

Question

2 answers

solution1 2 2013-12-20 13:29:53

solution2 1 2012-08-01 10:54:38

solution1
2 2013-12-20 13:29:53

solution2
1 2012-08-01 10:54:38