1. Sim Joo Pee
  2. PowerServer
  3. Monday, 4 December 2023 10:36 AM UTC

Hi All,

 Suddenly my cloud application has the "Session failed to respond 244 " error. The session timeout i set in application.json is 86400 seconds. But, my app isnt open for that long, it just less than 15 minutes. Can anyone please help? The server is not rebooted anyway. Thanks in advance.

Do I need to set this at application pool IIS?  https://docs.appeon.com/ps2022/Session_does_not_exist.html

I have Powerserver 2022 Build 1900.

Sim Joo Pee Accepted Answer Pending Moderation
  1. Thursday, 7 December 2023 01:36 AM UTC
  2. PowerServer
  3. # 1

Hi All,

   Thanks a lot for the information. However, i would like to know is it a must to change those default value to 0? Because currently i only have one website in this powerserver. There is no other site on the same server. Can i just leave it as the default value? The server has many RAM available.

Please advice. Thanks.

Comment
There are no comments made yet.
Sim Joo Pee Accepted Answer Pending Moderation
  1. Tuesday, 5 December 2023 14:18 PM UTC
  2. PowerServer
  3. # 2

Hi,

   Thanks a lot for the replied. I appreciate it a lot. By the way, i still dnt understand what is the different between the setting in application.json (see attachment) and the idle setting in the application pool advance settings?  Can you enlighten me? Thanks.

Attachments (1)
Comment
  1. Francisco Martinez @Appeon
  2. Tuesday, 5 December 2023 15:00 PM UTC
The timeout values in the application.json file controls the lifetime of the entities handled by the Web API (transactions, sessions, etc), while the timeout value in IIS governs the lifetime of the Web API itself. And when the Web API is killed, all the entities it handles are lost with it (transactions, sessions, etc)



Regards - Francisco
  1. Helpful 2
There are no comments made yet.
Sim Joo Pee Accepted Answer Pending Moderation
  1. Tuesday, 5 December 2023 00:52 AM UTC
  2. PowerServer
  3. # 3

Hi,

Thanks for the prompt reply. However, i didnt have this issue at the beginning, only after three months, it started to have this problem. How do i know if this is the root caused?? what value is the best to put here?

Thanks.

Comment
  1. Logan Liu @Appeon
  2. Tuesday, 5 December 2023 05:35 AM UTC
Hi Sim,

1) "How do i know if this is the root caused??"

It's IIS's default configuration to recycle after the specified time if you don't change any configuration.

Maybe you can try to find the logs for IIS application pool recycling in the Windows Event Log to prove this.

Refer to: https://support.secureauth.com/hc/en-us/articles/360019884311-How-to-enable-Application-Pool-recycle-logging-iis

https://stackoverflow.com/questions/9984604/how-to-find-app-pool-recycles-in-event-log.



You can't encounter this error every day because of the 1740 default value.

There is a blog about the 1740 minutes (29 hours) default value: https://weblogs.asp.net/owscott/why-is-the-iis-default-app-pool-recycle-set-to-1740-minutes



2) "what value is the best to put here?"

There is a suggestion in https://docs.appeon.com/ps2022/Session_does_not_exist.html:

Change the value of both the Idle Time-out (minutes) and the Regular Time Interval (minutes) options to 0.

Regards, Logan
  1. Helpful 2
There are no comments made yet.
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Monday, 4 December 2023 14:18 PM UTC
  2. PowerServer
  3. # 4

Hi Sim,

Yes, there are settings you need to check in IIS too, namely:

(Application Pool Advanced Settings)

 

Regards,

Francisco

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.