Session and request states hold context information inside of the session manager. The session state maintains the context of a logical connection with a client. The request state maintains the context of a running request inside a given session.

The session manager must acquire a connection to a multi-session agent and an ABL session in order to run a request. Multi-session agents, however, do not acquire connections. When started, multi-session agents are generally always waiting for requests.

Session states

A session state is maintained by the session manager. The session state can be viewed in OpenEdge Management or through the session information REST API. The session states can be displayed as:
  • INIT / STARTING–Indicates that the session is being initialized by the multi-session agent.
  • AVAILABLE–Indicates that a session is available for use. A session cannot be acted upon simultaneously by multiple threads.
  • RESERVED–Indicates that a session is running an active request and is unavailable to other processes.
  • STOPPING–Indicates that the session is awaiting the stopping processes to complete on the multi-session agent.
  • STOPPED–Indicates that the session has stopped. This state is displayed before the session is trimmed.

Request states

A request state indicates the messaging status between the session manager and the multi-session agent. The request state can be viewed in OpenEdge Management or through the current request information REST API. The request states can be displayed as:
  • INIT–Indicates the initiation of the request object in the session manager.
  • READY–Indicates that the multi-session agent has acquired a connection and ABL session necessary to run a request.
  • WRITING–Indicates that the client is sending packets of the request to the multi-session agent.
  • RUNNING–Indicates that the final packet of the client request was sent to the multi-session agent, but that the multi-session agent has not yet sent the first packet of the response.
  • READING–Indicates that the client request is in the process of receiving a response from the multi-session agent.
  • DISCONNECT–Indicates that the request is running a disconnect procedure.

For more information about viewing session and request states in OpenEdge Management or OpenEdge Explorer, see View OpenEdge ABL application client sessions in Manage Progress Application Server (PAS) for OpenEdge with OpenEdge Management.

For more information about viewing session and request states using the OpenEdge Manager REST APIs, see Get session information and Get current request information in PAS for OpenEdge Administration Tools Reference.

ABL Session states

Much like session and request states, the multi-session agent maintains state infromation about each ABL session it has. The ABL sessions states can be displayed as:

  • IDLE – Indicates that an agent session is available to run a request.
  • ACTIVE – Indicates that an agent session is running a request.
  • TERMINATED – Indicates that an agent session is no longer available.

For more information about viewing agent session states, see Get session metrics in PAS for OpenEdge Administration Tools Reference.