PASOE maxABLSessionsPerAgent and maxConnectionsPerAgent:
- These properties are configured in the {CATALINA_BASE}\config\openedge.properties under the global [AppServer.Agent] or specifically eg [AppServer.Agent.oepas1] Section.
- The maxABLSessionsPerAgent is between Session Manager and an MS-Agent which governs the pool of ABL sessions that can be used to process concurrent connections.
- The maxConnectionsPerAgent controls the maximum concurrent connection (session requests) per MSAgent
In general the maxABLSessionsPerAgent should be the same as maxConnectionsPerAgent, especially if the application is Session Free (state-free, stateless) where the agent session has no connection to a session manager (client) session unless it is running a request.
When running a Session Managed application, the maxABLSessionsPerAgent needs to be greater than maxConnectionsPerAgent. In this way one can control CPU usage, and still have client context that is persistent and awaiting the next request by a user not currently making a request. One will also have a proportionally larger amount of memory usage since the sessions are higher than concurrent connections.
How would maxABLSessionsPerAgent and maxConnectionsPerAgent work?
maxABLSessionsPerAgent=100
maxConnectionsPerAgent=20
- 100 users who login in first thing in the morning, use the application sporadically during the day, and log off at night. PASOE has no connection state. The client connects using HTTP/S always and controls ABL session
- 20 max concurrent connections (maxConnectionsPerAgent) to the single MSAgent in use. This means the CPU of the multi-session agent is limited by 20 concurrent requests running at a given time.
- The context for the 100 users is kept in the Session Manager. When a connection becomes available, the next request can be processed with an expec.ed context by the ABL Session in the MSA.
A new MSA is started when more
maxConnectionsPerAgent are needed, this is further clarified in Article:
