[freenet-support] http fproxy ports are not closed

2011-08-31 Thread Dennis Nezic 
netstat (netstat -pnat | grep java) shows 213 connections to my fproxy
at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after I
could no longer access fproxy -- probably because of some thread or
connection limit. I'm not exactly sure how to reproduce this -- it's
not simply a matter of opening a connection to fproxy.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Re: [freenet-support] http fproxy ports are not closed

2011-08-31 Thread Dennis Nezic 
On Wed, 31 Aug 2011 09:44:17 -0400, Dennis Nezic wrote:
 netstat (netstat -pnat | grep java) shows 213 connections to my fproxy
 at 127.0.0.1:, in a CLOSE_WAIT state. I only noticed this after
 I could no longer access fproxy -- probably because of some thread or
 connection limit. I'm not exactly sure how to reproduce this -- it's
 not simply a matter of opening a connection to fproxy.

False alarm. I think my freenet wget spider got out of control.
Apologies.
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe