> Any Idea what could cause this? There were only 15 users in the test.
Is this an automated test that hammers the server? I ran into a similar situation on Linux. The problem is that when a TCP connection is closed the socket on one side ends up in the TIME_WAIT state. This is just in case a packet was lost closing the connection. The socket stays like this for 30 seconds (I think). Also a socket takes up a file handle so opening/closing a lot of TCP connections eats up your file handles. To get a list of sockets in the TIME_WAIT state run the netstat command. If you see a ton of them just after the server starts to fail then this is your problem. I think your options are to either up the maximum number of file handles, decrease the TIME_WAIT delay, or don't hit the server so hard. -- View this message in context: http://www.nabble.com/Too-many-open-Files-tf4440829.html#a12684950 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
