Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved PowerServer 2022 Session Error/Timeout

  1. Issue
0
Votes
Undo
  1. Thomas Rolseth
    Thomas Rolseth
  2. PowerServer
  3. Thursday, 26 January 2023 17:05 PM UTC

We recently migrated a PB 2019 application to 2022 and also deployed it to PowerServer.  It's been working very well.  However, one user reported an issue recently.  The user stated that the app was started and used without issue for a while.  It was then left idle for 30 minutes or so.  When he started working on it again the attached error message appeared.  The application connects to an Oracle database and we increased the transaction timeout in the web api's applications.json file to 3600 (this was done before this error was reported).

Does anyone have any thoughts on the root cause and a workaround?  A more graceful way to deal with an error like this?

Thanks, Tom

Attachments (1)
ps_session_error.JPG ps_session_error.JPG
  1. Oracle
  2. PowerBuilder
  3. PowerServer
  4. Session
  5. Transaction
PB2022 PowerServer Project Painter only recognizes...
duplicate error 'DataWindow' attribute
Responses (3)
Logan Liu @Appeon
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 31 January 2023 07:19 AM UTC
  2. PowerServer
  3. # 1

Hi Thomas,

There are two common causes for the session doesn't exist error:

1) Is the Web API application deployed on IIS? The default recycle settings for the IIS application pools may cause the session to become invalid. To resolve it, refer to: https://docs.appeon.com/ps2022/Session_does_not_exist.html

2) Have you ever reduced the Session timeout setting? By default, the timeout period for a session is 3600 seconds. Refer to: https://docs.appeon.com/ps2022/Configure_timeout_settings.html

Regards, Logan

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Thursday, 26 January 2023 17:30 PM UTC
  2. PowerServer
  3. # 2

there are various timeouts that you need to be aware of.  If your users will be idle for 30+ minutes, you should either log them out of the PB application automatically or add code to hit the database every so often to keep the session alive.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 January 2023 17:14 PM UTC
  2. PowerServer
  3. # 3

Hi Thomas;

  I suspect that it was a "session" timeout and not a DBMS timeout. Try increasing the session timeout on the App server.  HTH 

Regards ... Chris.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.