On Sat, Sep 18, 2004 at 05:46:59AM -0400, Steve Job wrote: : I get: : SEVERE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] : ignored exception: java.net.SocketException: Too many open files : java.net.SocketException: Too many open files
Someone else mentioned ulimit. You could also look into tuning your network stack. Most OSs default to a very high wait time on closing disconnected sockets. For machines that serve large numbers of short-lived connections (e.g. web servers) this can produce the very problem you've experienced. Reduce the TIME_WAIT interval, which should reduce the number of sockets in CLOSE_WAIT state. Since sockets == handle == "file" in the Unix sense, this should reduce the number of files you have open at any given time. For Solaris the ndd param is tcp_time_wait_interval; in Linux it's somewhere under /proc/sys/net/ (aka "sysctl net.something.other"). -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
