JAVA restart necessary to fix inactive Minimserver?

[hvaleton]

(07-06-2013 13:17)simoncn Wrote:  

(07-06-2013 10:05)hvaleton Wrote:  192.168.1.57 is my Galaxy Nexus smartphone

Thanks for all the very detailed information. What control point or other audio software are you running on the Galaxy Nexus?

BubbleDS
MediaHouse
Sonos (but that AP does not 'see' the MinimServer)

(07-06-2013 13:17)simoncn Wrote:  In the latest netstat output, this device has 14 established HTTP connections to Minimserver. I can't think of any good reason for this, and I think it's likely to be the cause of the descriptor leakage problem.

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...