JAVA restart necessary to fix inactive Minimserver?

[simoncn]

(07-06-2013 15:08)hvaleton Wrote:  Very strange behaviour: after switching off my Nexus the netstat command output still showed the 14 established connections to 192.168.1.57, same as before the switch-off.

Could it be that it takes some time for these connections to disappear from the netstat output?
Should I perhaps restart the MinimServer? Or even the Qnap?

I ran netstat from my Nexus and have enclosed the output as an attachment.
It does not show any connections with the Qnap whose ip is 192.168.1.44.

I'm completely puzzled now...

I will try BubbleDS and MediaHouse to see if I can reproduce this behaviour. My guess is that these connections are used by the control point to download album art files, and the control point is leaving them open indefinitely after the album art download has completed. The correct behaviour would be for the control point to close these connections after a reasonable period such as 5 or 10 minutes.

Also, it seems that the QNAP is failing to close and release socket connections that have been "abandoned" by a powered-off client. My recollection is that Linux has a very long default timeout (120 minutes) before it starts sending keep-alive probes to see if the client is still there.