Jim,
Thanks for the prompt (and informative)
reply; we've eliminated the call from our monitoring and the servers seem much
more stable.
It makes intuitive sense that this would be
a difficult function to implement in a thread-safe fashion, but I have to agree
that it would be better if this fact were called out in big bold type
somewhere in the API documentation. I've submitted a documentation bug in SourceForge
(#745784); let me know if there is anything else I can/should do.
Eric
-----Original Message-----In a message dated 5/29/2003 2:28:56 AM Eastern Daylight Time, [EMAIL PROTECTED] writes:
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]On Behalf Of Jim Davidson
Sent: Thursday, May 29, 2003 8: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/
