Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

How do we set all FCM timeout?

SA-5879

Summary



Clarification is requested how to setup the following timeout for FCM.
On the main application:
  • Authentication timeout (access group)
  • Passivation timeout ( requestor)
  • Requestor passivation expiry.
  • Websphere session timeout
Same timeout question for the node accessed remotely:
  • Authentication timeout (access group)
  • Passivation timeout ( requestor)
  • Requestor passivation expiry.
  • Websphere session timeout
 
On the prgateway:
  • IAC timeout set via the web.xml
  • IAC timeout via UI in the gateway console.

Resolution


In this particular case, the remote node is only accessed via FCM/IAC and never directly.
The authentication timeout is not answered here as it is more complex and we investigate it via dedicated SR-122391.
Passivation timeout:
The passivation timeout is used to prevent PRPC to consume too much memory on the application server.
The idea is to set this value not too high so that the application server doesn't consume too much memory (for PRPC session) and not too low so that the user experience is not impacted in terms of performance.
During re-activation of passivated data, the user will experience a delay compared to the case where the data is still in memory.
So really this value is a trade between memory and user experience.
 
By default, PRPC is configured with a requestor passivation at 60 minutes, with means thread passivation of 30 minutes and page passivation of 15 minutes.
So passivation is happening progressively.
This is typically fine as a general rule a user can be considered as having stopped working on an application when he has no interacted for 1 hour (we have to draw a line somewhere).
Of course these values can be changed, if it turns out they are not appropriate based on your user behaviour and/or memory usage.
We recommend the remote node to have the same settings as the main node.
  
Requestor passivation expiry:
Default setting should be fine for both main node and remote node. Increase it if you wish your user to resume a session which is more than 1 day old. The higher the value is, the bigger the passivation folder will be.
 
IAC timeout:
For the prgateway session timeout, configure the one which is shown in the prgateway UI.
This setting defines the HTTP session timeout for your FCM gadget.
We recommend this value matches the passivation timeout setting.
 
Websphere session timeout:
This settings should therefore be setup and tuned by the Webshere administrator based on memory used and performance, rather than being recommend by Pegasystems as this is transparent for PRPC and is not impacting the PRPC session.
 
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us