Kbase P37278: Where can the Status of an AppServer be found.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/08/2010 |
|
Status: Verified
GOAL:
Where can the Status of an AppServer be found.
GOAL:
What are the Definitions for the Status specifics of an AppServer.
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1x
OpenEdge 10.x
FIX:
Viewing the Status of an AppServer
The status of any running AppServer instance may be viewed through the Progress Explorer.
Each AppServer instance provides a separate status view, the status of multiple AppServers may be monitored simultaneously. Instances running on the same or different machines may be monitored.
Application Server processes may be added or trimmed from the AppServer Status dialog box.
To view AppServer status:From the Progress Explorer's tree view, select the AppServer instance whose status is to be viewed and do one of the following:
· Right-click the broker. A shortcut menu appears; choose Status.
· Click the Status button.
· Choose Action>Status.
The Summary Tab
The Summary tab provides the following status specifics:
· Broker Name - The name of the selected Application Broker.
· Operating Mode - The operating mode of the selected AppServer (state-reset, state-aware, or stateless).
· Broker Status - The current execution state of the Application Broker.
· Broker Port - The TCP/IP port number that the Application Broker listens to.
· Broker PID - The process ID of the Application Broker.
· Active Servers - The number of active Application Servers.
· Busy Servers - The number of Application Servers that are busy serving remote requests.
· Locked Servers - The number of Application Servers that are handling remote requests for a single client connection. For a state-reset or state-aware AppServer, this is the number of all active servers. For a stateless AppServer, this is the number of servers that are servicing a bound connection.
· Available Servers - The number of Application Servers that are available to handle requests.
· Active Clients (now, peak) - The current and peak number of connected clients since the AppServer was started.
· Client Queue Depth (cur, max) - The number of clients waiting for agents to become available to service their request. The current value (cur) represents the number of waiting clients at the moment the status is displayed, and the maximum value (max) represents the largest number of clients waiting concurrently since the broker was started.
· Total Requests - The total number of client requests since the AppServer was started.
· Rq Wait (max, avg) - The maximum and average wait time for service per client request since the AppServer was started.
· Rq Duration (max, avg) - The maximum and average completion time for each client request since the AppServer was started.
The Details Tab
The Details tab provides in a table a detailed report on Application Server processes. Each row in the table contains the detail status of a single, active Application Server process:
· PID - The process ID of the server process.
· State - The current execution state of the server process.
· Port - The TCP/IP port number used by the server process.
· nRq - The number of messages sent .to the server process.
· nRcvd - The number of messages received by the server process.
· nSent - The number of requests sent by the server process.
· Started - The time stamp indicating when the server process started.
· Last Change - The time stamp indicating when the server process last changed execution state..