ASBMAN-clientdetail reports an Agent PID and Agent port for connections that do not have an active request

ASBMAN -clientdetail reports an Agent PID and Agent port for connections that do not have an active request. Documentation states these should be reported blank in this case.

Feb 21, 2019
Knowledge

Title

URL Name

000046799

Article Number

000169925

Environment

Product: OpenEdge Version: 10.2x, 11.x OS: All supported platforms Other: AppServer

Question/Problem Description

AppServer in stateless / state-free operating mode.
ASBMAN -clientdetail shows Agent PID and Agent Port fields have values for all connections
Some Client connections report an Agent PID and Port that no longer exist in the system
Multiple Client connections report the same Agent PID and Agent Port values

OpenEdge Application Server: Administration, Appendix B: Command and Utility Reference, section ASBMAN

agent PID: The process identifier of the AppServer agent actively servicing a request from the specified client. Blank if no request is active.
agent port number: The listening port number of the AppServer agent actively servicing a request from the specified client. Blank if no request is active.

ASBMAN -clientdetail infers that the Number of clients connected is larger than number of Agents.
There should be connections that report blank Agent PID and Agent port number that are not actively servicing a request

Steps to Reproduce

Clarifying Information

1. Run the following to create AppServer connections. During the PAUSE, run the following asbman commands:

DEFINE VARIABLE i AS INTEGER     NO-UNDO.
DEFINE VARIABLE h AS HANDLE      NO-UNDO EXTENT 20.

DO i = 1 TO 10:
    CREATE SERVER h[i].
    h[i]:CONNECT("-AppService asbroker1").
END.

PAUSE.

DO i = 1 TO 10:
    h[i]:DISCONNECT().
    DELETE OBJECT h[i].
END.

2. Capture a snapshot of AppServer status and a list of clients in the connection pool.
As expected, this will list 10 active clients [Total Requests], with 5 available agents (default asbroker1 configuration).

$ asbman -i asbroker1 -query
$ asbman -i asbroker1 -listclients

3. Capture the client details.

The "agent PID" and "agent port" fields have values, while there are no requests being run.
The same Agent PID and Agent Port values are reported for some clients

$ asbman -i asbroker1 -clientdetail 2
$ asbman -i asbroker1 -clientdetail all

4. Trim the agents, re-run client detail on the second connHdl and AppServer Broker status:

The -clientdetail output will still be identical to that of Step 3, even though agent has been trimmed
The Client connection details incorrectly reports an Agent PID and Agent Port values that no longer exist
The AppServer Broker status correctly reports 20 active clients [Total Requests], with 0 available Agents

$ asbman -i asbroker1 -trim 5
$ asbman -i asbroker1 -clientdetail 2
$ asbman -i asbroker1 -query

Error Message

Defect Number

Defect PSC00289575

Enhancement Number

Cause

The Agent PID and Agent Port fields are initially reported as those which the clients in the connection pool are queued.
These fields are not blanked out when a request for a connection/client finished.
They ASBMAN -clientdetail keeps reporting the values for either the agent the client was queued on or the last request they made after that request finished, even if the agent is subsequently trimmed

Resolution

None at this time.

Workaround

None at this time.

Notes

Keyword Phrase

Last Modified Date

2/21/2019 1:53 PM

ASBMAN-clientdetail reports an Agent PID and Agent port for connections that do not have an active request

Files(0)

Was this article helpful?

Was this article helpful?

ASBMAN-clientdetail reports an Agent PID and Agent port for connections that do not have an active request

Information

Related Articles