All,
We have been trying to debug occasional (1-4 times/day) unexplained server
crashes under moderate load. Our most recent testing points fairly strongly
to the command "[ns_server all]" which occurs in a trace filter we run for
system monitoring purposes. We are currently testing an updated version of
the filter which omits this command, but I would still be interested to know
if anyone has encountered instability with the use of ns_server in their
environment. The relevant snippet of code looks something like this:
-------8<-------
if { [catch {set current_count [llength [set tmp [ns_server all] ] ] }
errmsg] } {}
ns_log Error "filter_conn_count: $errmsg\n\[ns_server all\] returned
this:\n$tmp"
return filter_ok ;# drop the sample on the floor
}
set max_count [nsv_get max_conn_count value]
if { $current_count > $max_count } {
nsv_set max_conn_count value $current_count
}
-------8<-------
We are running AOLserver 3.4.2 on Linux with a forward-ported version of the
ArsDigita AD+13 encoding patch.
Thanks in advance for any help.
Eric
__________________________
Eric Larkin
Chief Technology Officer
Arena Solutions
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
