Feedback
Did this article resolve your question/issue?

   

Article

PASOE failures after a period of inactivity

« Go Back

Information

 
TitlePASOE failures after a period of inactivity
URL Namepasoe-failures-after-a-period-of-inactivity
Article Number000117449
EnvironmentProduct: OpenEdge
Version: 11.7.x
OS: Windows
Other: .Net OpenClient, Java OpenClient, PASOE
Question/Problem Description
PASOE clients .NET open and JAVA running with APSV transport fails with an error message after a period of inactivity. 

The PASOE clients use a session-free connection to PASOE as classic "state-free" broker.

 
Steps to Reproduce
Clarifying Information
Application using APSV transport.

In the application log for the PASOE application there are multiple entries for "unable to find existent HTTP session", see error message section.

No load-balancing in the configuration.

Application migrated from Classic AppServer to PASOE. Application works in classic AppServer by setting the session-free and timeout.

 
Error MessageThe error message is "Communication layer message: General Error. 9998".  

Communication layer message: <message text>. (7175)

"unable to find existing HTTP session for specified sessionID"

<anytimestamp> [catalina-exec-3] ERROR c.p.appserv.adapters.apsv.Request - APSV(EC7DB1DA9830A7F3684CF43916EC816DE9A9880A0B69.oepas1) : unable to find existing HTTP session for specified sessionID. (18328)
<anytimestamp> [catalina-exec-3] ERROR c.p.appserv.adapters.apsv.Request - APSV(EC7DB1DA9830A7F3684CF43916EC816DE9A9880A0B69.oepas1) : An error occurred processing the POST request :  Unexpected error : com.progress.appserv.broker.exception.BrokerException$SessionNotFoundException: Session. (18320)
Defect/Enhancement Number
Cause
Failures due to HTTP Session expiration.
The way of OpenEdge 11.7 is designed does not allow to use the session-free at this moment.
Resolution

Starting with OpenEdge 12.0 a new APSV protocol has been introduced and does exactly what is intended for this scenario.
Workaround
For releases up to OpenEdge 11.7, use one of the following workarounds:
  1. Turn off HTTP Sessions in OpenEdge.Properties file. By doing this will preclude the use of load balancers for APSV.
Go to OpenEdge.Properties file and change the useHTTPSession from 1 to 0  (OpenEdge.Properties -> useHTTPSessions=0)
or
  1. Extend HTTP Session timeout to a length acceptable for the user application.
For APSV, this is done through the idleSessionTimeout property in openedge.properties. This value is used for APSV regardless of the idleResourceTimeout value.
Set the session-timeout with a higher value, for example 3000 minutes.
or
  1. Build a background .NET process to ping the connection to ensure it's alive.
Notes
Last Modified Date11/20/2020 7:11 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.