PASOE Session Manager HTTP sessions are not properly terminated via OEM

When a Session Manager HTTP session is terminated via OE Management / Explorer and the client uses the session-free session model, then the client can still continue using this session without any issues. So the session is not properly terminated. Instead of throwing an error, the PASOE instance will create a new HTTP session with the same session ID and continues to process the requests from the client.

 

OE Management / Explorer uses the REST API to terminate the session, but what makes the request from OEM special is the sequence of REST API calls that it performs:

1) List available sessions
2) Terminate the session
3) List available sessions

Normally a user would simply perform steps 1 and 2, but step 3 is what seems to prevent the session from being properly terminated.

If the session is properly terminated, then the following error should be returned by an ABL client:
 
From a .NET Open Client the following error is returned:
 
The PASOE Session Manager log file (e.g. oepas1.<date>.log) will show the following error:
 

The exact cause is not known at this time.
 

Until the fix is available, use the workaround below.
 

Follow these steps:

• Determine the Session Manager (HTTP) session ID for this request. For example:
  • Find the session ID in the Client Sessions page within OE Management / Explorer.
  • Use the REST API to list the available sessions (see https://docs.progress.com/bundle/pas-for-openedge-reference-122/page/Get-session-information.html ).
  • Find the session ID in the localhost-access.{date}.log file.
• Use the REST API to terminate the session that was just created (see https://docs.progress.com/bundle/pas-for-openedge-reference-122/page/Terminate-a-session.html ).