Difference between revisions of "Ns server"

From AOLserver Wiki
Jump to navigation Jump to search
Line 28: Line 28:
  
 
: See [http://sourceforge.net/tracker/index.php?func=detail&aid=745784&group_id=3152&atid=103152 Bug #745784] -- '''ns_server''' is not safe under load because: "The problem is either the connPtr or some of the data buried in the conn can be changing in the running connection thread.  I wouldn't suggest this be fixed because it could complicate the code and introduce a performance problem."
 
: See [http://sourceforge.net/tracker/index.php?func=detail&aid=745784&group_id=3152&atid=103152 Bug #745784] -- '''ns_server''' is not safe under load because: "The problem is either the connPtr or some of the data buried in the conn can be changing in the running connection thread.  I wouldn't suggest this be fixed because it could complicate the code and introduce a performance problem."
 +
 +
: In AOLserver 4.5, a thread race condition which could lead to a crash when using "ns_server threads" has been fixed.
 +
  
 
'''EXAMPLES'''
 
'''EXAMPLES'''

Revision as of 00:55, 4 October 2009

Man page: http://aolserver.com/docs/tcl/ns_server.html


NAME

ns_server - Get state of the server's connection pools and queues

SYNOPSIS

ns_server option ?pool?

DESCRIPTION

This command provides a way to examine the current server's connection pools and queues. The legal options (which may be abbreviated) are:
  • ns_server active ?pool?
  • ns_server all ?pool?
  • ns_server connections ?pool?
  • ns_server keepalive ?pool?
  • ns_server pools ?pool?
  • ns_server queued ?pool?
  • ns_server threads ?pool?
Returns a list of key-value pairs identifying the number of connection threads and what state they are currently in.
  • ns_server waiting ?pool?

NOTES

See Bug #745784 -- ns_server is not safe under load because: "The problem is either the connPtr or some of the data buried in the conn can be changing in the running connection thread. I wouldn't suggest this be fixed because it could complicate the code and introduce a performance problem."
In AOLserver 4.5, a thread race condition which could lead to a crash when using "ns_server threads" has been fixed.


EXAMPLES

   % ns_server threads
   {min 0} {max 10} {current 0} {idle 0} {stopping 0}

SEE ALSO


-