Question
Users are not able to work on a case after 45 mins
We have Pega 7.1.9 and the timeout setting as below;
env name="timeout/application" value="600" />
<env name="timeout/browser" value="1800" />
<env name="timeout/portal" value="600" />
even though the browser timeout is set as 1800, user is bale to work on cases post being idle on the case for 30 mins, but cannot work post 45 mins. We do not have anything on logs but from fiddler it looks like that the session is timing out. We need to get rid of this issue and have to allow the user to work on a case for being idle for even 4 hrs, without getting an exception.
Can someone help.
***Updated by moderator: Lochan to add Categories***
Pegasystems Inc.
US
Hi,
Add/modify the following prconfig setting, restart the JVMs and see if that helps.
<env name="timeout/browser" value="21600" />
<env name="initialization/persistrequestor" value="OnTimeout" />
Also, if you have a Load balancer routing requests to the JVMs ensure that you have Session affinity turned ON/enabled.
JP Morgan Chase
US
Ankur,
What does these setting signify and what behavior these would cause to servers..also last thing are these time in second or millisecond:-
| <env name="timeout/browser" value="1920" /> |
| <env name="timeout/portal" value="1920" /> |
| <env name="timeout/page" value="420" /> |
| <env name="timeout/thread" value="1800" /> |
Pegasystems Inc.
US
timeout Category
The timeout category defines the length of time that a context can be inactive before it is
passivated.
timeout/application
Type: integer
Default: 600
Functionality: This entry specifies the timeout value, in seconds, that all
requestors used by services can be idle before they are passivated.
NOTE: This value does not include portlet services (Rule-Service-
Portlet). The timeout value for Portlet services is set with the
portal entry described below.
Available since: Version 4.1
timeout/browser
Type: integer
Default: 3600
Functionality: This entry specifies the timeout value, in seconds, that all
requestors used by human users ("interactive" users) may be idle
before being passivated.
Available since: Version 4.1
timeout Category
The timeout category defines the length of time that a context can be inactive before it is
passivated.
timeout/application
Type: integer
Default: 600
Functionality: This entry specifies the timeout value, in seconds, that all
requestors used by services can be idle before they are passivated.
NOTE: This value does not include portlet services (Rule-Service-
Portlet). The timeout value for Portlet services is set with the
portal entry described below.
Available since: Version 4.1
timeout/browser
Type: integer
Default: 3600
Functionality: This entry specifies the timeout value, in seconds, that all
requestors used by human users ("interactive" users) may be idle
before being passivated.
Available since: Version 4.1
timeout/page
Type: integer
Default: 900
Functionality: This entry specifies the timeout value, in seconds, when pages will
be passivated.
NOTE: This setting is linked to the thread and browser settings in
the timeout category.
• If this setting is added to the prconfig file, the specified value will
be used.
• If this setting is not specifically added to the prconfig file, but the
thread setting is specified, the page setting will be half that value.
Example: If the thread setting is specified to be 800 seconds, the
page value will default to 400 seconds.
• If the thread setting is not specified, but the browser setting is
specified, then the thread setting will default to half the browser
value, and the page value will default to half of the thread setting.
Example: if the browser setting is specified to be 1200 seconds,
then the thread value will default to 600 seconds, and the page
value will default to 300 seconds.
Available since: Version 5.5
timeout/portal
Type: integer
Default: 3000
Functionality: This entry specifies the timeout value, in seconds, that all
requestors used by portlet services (Rule-Service-Portlet) may be
idle before being passivated. NOTE: This entry should be set to
the same value as the "browser" setting.
Available since: Version 4.1
timeout/thread
Type: integer
Default: 1800
Functionality: This entry specifies the timeout value, in seconds, that threads
within a requestor may be idle before being passivated.
NOTE: This setting is linked to the browser settings in the
timeout category.
• If this setting is added to the prconfig file, the specified value will
be used.
• If this setting is not specifically added to the prconfig file, but the
browser setting is specified, the thread setting will be half that
value. Example: If the browser setting is specified to be 800
seconds, the thread value will default to 400 seconds.
Available since: Version 5.5