Are you sure it isn't your OS killing your server? Unix tends to do
this when it runs out of resources, and it often kills the process
using the most resources first.
Jim
>
> The nssock notice is apparently benign. (I found the code after all. I
> needed to include .cpp files in my grep.)
>
> Here's the real problem. Under heavy load, we're consistently getting this
> behavior: The server suddenly kills all its conn threads (but not the
> aolserver system threads), and does not reopen them without being restarted
> manually. This happens across 4 servers, at approximately the same time,
> after about 40 minutes.
>
> Our load test peaks at 15 minutes, and our cache timeouts are set to 60
> seconds. The app continues to work fine until about the 40 minute point
> each time, before deciding to kill all its threads.
>
> No errors are reported.
>
> Does anyone have any idea what could cause this to happen?
>
> Thanks,
> Sean
>
