JAVA restart necessary to fix inactive Minimserver?

[simoncn]

(07-06-2013 18:29)simoncn Wrote:  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.

I don't think these connections from 192.168.1.57 are causing the large number of leaked sockets in the lsof output. I can see these connections in lsof as well as the leaked sockets (marked as "can't identify protocol"). From doing some web searching, it seems the leaked sockets are "half closed" and don't show up in the output from netstat.

I've tried using BubbleDS and MediaHouse, and neither of these seems to cause any leaked sockets to be created. I'll continue to investigate what might be creating the leaked sockets.