Netscape NETSCAPE DIRECTORY SERVER 6.02, Administrator'S Manual

Page: 401 / 568

Monitoring Server Activity
Chapter 12 Monitoring Server and Database Activity 401
Connection Status
The Connection Status table in the Directory Server Console provides the following
information about the amount of resources in use by each currently open
connection:
Threads Waiting to Write to
Client Total number of threads waiting to write to the client. Threads may not be
immediately written when the server must pause while sending data to a
client. Reasons for a pause include a slow network, a slow client, or an
extremely large amount of information being sent to the client.
Threads Waiting to Read
from Client Total number of threads waiting to read from the client. Threads may not be
immediately read if the server starts to receive a request from the client and
then the transmission of that request is halted for some reason. Generally,
threads waiting to read are an indication of a slow network or client.
Thread Concurrency Meaningful on Solaris 2.x only. Provides an indication of the level of thread
concurrency.
Databases in use Total number of databases being serviced by the server.
Table 12-3 Server Performance Monitoring - Connection Status
Table Header Description
Time opened Indicates the time on the server when the connection was initially opened.
Started Indicates the number of operations initiated by this connection.
Completed Indicates the number of operations completed by the server for this
connection.
Bound as Indicates the distinguished name used by the client to bind to the server. If
the client has not authenticated to the server, the server displays
not
bound
in this field.
Read/Write Indicates whether the server is currently blocked for read or write access to
the client. Possible values include:
• Not blocked. Indicates that the server is idle, actively sending data to the
client, or actively reading data from the client.
• Blocked. Indicates that the server is trying to send data to the client or
read data from the client, but cannot. The probable cause is a slow
network or client.
Table 12-2
Server Performance Monitoring - Current Resource Usage (Continued)
Resource Current total