P
Paul Connaughton
Guest
The openedge.properties.README is clear about which session the properties control. See below. There appears to be a disconnect between the README and the OE doc that OEM pulls its context help from. As Matt mentioned, Defect ADAS-12871 has been logged for this. At this time, the only way to terminate an idle ABL session is with REST/JMX call. There is an existing backlog item for ABL session timeout functionality, but it wouldn't hurt to log an IDEA on communities for this. Paul oe.prop definitions: idleResourceTimeout=0 Timeout value in milliseconds to determine the frequency with which the PASOE server checks for idle resources. Any resource (e.g. connection, agent, or client session) that has not been accessed more recently than the specified timeout for that property will be terminated. If this property is set to zero, then idle resource checking is disabled. idleSessionTimeout=300000 Timeout value in milliseconds for an idle SessionManager session. If a SessionManager session is idle for more than the specified timeout value, then the session will be deleted when idleResource cleanup is done. idleAgentTimeout=300000 Timeout value in milliseconds for an idle agent. If an agent is idle for more than the specified timeout value, then the session will be deleted when idleResource cleanup is done. idleConnectionTimeout=300000 Timeout value in milliseconds between an AppServer client and the Session Manager. If a connection is idle for more than the specified timeout value, then the SessionManager will terminate the connection by automatically disconnecting the connection from the AppServer.
Continue reading...
Continue reading...