Jim, I have a simple client/server application that is using SDP. The client opens several threads. Each of these threads connects to a server and send a chunk of bits. Nothing fancy.
Now I noticed that when I run sdpnetstat on the server's side, I see all the SDP connections disappear once the client is dead. But on the client's side I see these lines remain in the sdpnetstat output: Proto Recv-Q Send-Q Local Address Foreign Address PID/Program name ... sdp 0 0 11.4.3.156:54601 11.4.3.157:dnp - sdp 0 0 11.4.3.156:54602 11.4.3.157:dnp - sdp 0 0 11.4.3.156:54603 11.4.3.157:dnp - sdp 0 0 11.4.3.156:54604 11.4.3.157:dnp - ... While the client is alive, sdpnetstat looks ok: Proto Recv-Q Send-Q Local Address Foreign Address PID/Program name ... sdp 0 123004 11.4.3.156:54601 11.4.3.157:dnp 7773/client sdp 0 237776 11.4.3.156:54602 11.4.3.157:dnp 7773/client sdp 0 113072 11.4.3.156:54603 11.4.3.157:dnp 7773/client sdp 0 229376 11.4.3.156:54604 11.4.3.157:dnp 7773/client ... Once these orphan connections appear, they never disappear - only new orphans are added to the list from time to time. Any idea what is going on here? Is this bug or feature? -- Yevgeny _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
