Information

Title	idleSessionTimeout feature fails when using HTTP sessions with APSV transport

URL Name	idleSessionTimeout-feature-fails-when-using-HTTP-sessions-with-APSV-transport

Article Number	000118804

Environment	Product: OpenEdge Version: 11.7.x OS: All supported platforms Other: PASOE

Question/Problem Description

idleSessionTimeout feature fails when using HTTP sessions with APSV transport

Steps to Reproduce	Deploy a PASOE instance with APSV transport enabled. Specify an idleSessionTimeout value in the openedge.properties. Run a client program that connects via APSV that does the following: - Connect to the PASOE server - Run an RPC - Wait until after the idle session timeout has expired - Run a second RPC The second RPC should fail, but it doesn't.

Clarifying Information

Error Message	LocalSession(<sessionID>) : timeout error occurred while reserving a connection = <exception>. (18298)

Defect Number	ADAS-4312

Enhancement Number

Cause

Using the idleSessionTimeout feature with the APSV transport fails to work properly when using HTTP sessions. In this configuration, the APSV transport is supposed to set the idleSessionTimeout value (specified in the openedge .properties file) in each HTTP session, relying on Tomcat to detect when the session times out rather (than the PASOE idle resource watchdog). However, regardless of what value is set for idleSessionTimeout in the properties file, the timeout value is never set in the HTTP session.

The problem is caused by the fact that the APSV transport is looking for the idleSessionTimeout property in the APSV transport section of the property file rather than in the session manager section where it is defined. This can be confirmed by manually adding an idleSessionTimeout property in the APSV transport section. If the property is defined in the APSV transport section, then the idle session timeout works properly.

Resolution

Update to 11.7.4 or later.

Workaround

As a workaround, add an idleSessionTimeout property definition to the APSV transport section of the openedge.properties file.
Example:

[oepas1.ROOT.APSV]
adapterEnabled=1
enableRequestChunking=1
useHTTPSessions=1
# Workaround until fixed by ADAS-4312
idleSessionTimeout=300000

Notes

References to other documentation:

Progress article(s):
Changing idle session timeout option has no effect in PASOE

Keyword Phrase

Last Modified Date	3/10/2022 3:38 PM