Is this also true for all the other
ns_server commands like [ns_server connections] or [ns_server active] ?
Because we are using these
extensively for monitoring and performance analysis. It seems the only time
we've had crashes due to use of [ns_server all] is when there were lots of
waiting threads (in the backlog) in a heavy load situation. I agree that
"ns_server all" may not be very stable but it'll be useful to know if all the
there ns_server parameters may not be stable either.
Thanks,
-Seena
-----Original Message-----In a message dated 5/29/2003 2:28:56 AM Eastern Daylight Time, [EMAIL PROTECTED] writes:
From: Jim Davidson [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 29, 2003 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: [AOLSERVER] Instability with [ns_server all] under moderate load?
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:
Hi,I don't believe "ns_server all" is thread safe and it would be expensive to make it so. It's designed for occasional use in a debugging context, not as part of regular connection processing. The docs should probably be updated to make this clear.-Jim-- 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/
-- 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/
