So far things look good. The server continues to respond even after
being up for 12+ hours. It used to stop responding after a day or so.
There is still only one nsd process running. Should there only be one
nsd process when I am running mulptiple threads?! I am used to having a
seperate nsd8x process for every connection and thread.
Nate
Scott S. Goodwin wrote:
Sounds like you're experiencing thread stack corruption. Increase your
per-thread stacksize and see if the problem still exists.:
ns_section "ns/threads"
ns_param stacksize [expr 128*1024]
/s.
-----------------------------------------------------------------------
Scott S. Goodwin
e: [EMAIL PROTECTED] | u: http://scottg.net
aim: scottgnet
----- Original Message -----
From: "Nate Haggard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 23, 2002 3:37 PM
Subject: [AOLSERVER] 3.5.1 no response from webserver and only one nsd
process
We recently upgraded to AOLserver 3.5.1 from 3.4.2. 3.5.1 behaves
strangely. The first odd thing is that there is only one nsd process
instead of a seperate nsd8x process for every thread like in 3.4.2. The
second weird behavior is that the server works for a while, but then
suddenly stops responding to requests.
Our tcl code has a large number of ns_schedule_daily -thread calls. Has
this call changed in 3.5.1?
Nate
