CA Service Management

ours is AA environment.

we are not getting session timeout warning message on our APP server

when checked the folder bopcfg/www/ we dont find web.cfg but instead we found

web.cfg.update
web.cfg.tpl
primary-web3.cfg
primary-web2.cfg
primary-web5.cfg
primary-web4.cfg

In all the above mentioned files the session timeout and session timeout warning messages are mentioned as below:

# Timeout specifies the maximum number of minutes a user's session can be
# inactive before it is cancelled and all resources released.  After this
# period has elapsed, the user must start a new session by logging in again.

Timeout 90

# TimeoutWarning specifies the number of minutes prior to session timeout
# that the web client should pop up a warning alert box.  THe default value
# is five minutes; specify TimeoutWarning 0 to suppress this feature

! TimeoutWarning 5

can you help why we are not getting warning message before session timeout

You seemed to say for those app servers, there is not web cfg file? Those couple of cfg files seem are for primary server(background server) judging by their names.

Maybe you should open a Support case.  

Hi,

Please note the exclamation mark in front of the time warning...

Remove it fot the warning to take effect in each corresponding cfg file and adapt the time base on your need.

Please note that this is minutes related to the time out itself = x minutes prior the timeout time

i.e

Timeout 90

TimeoutWarning 5

"will result to receive a warning after 85 mn

hope this help.

/J

Hi Mayer,

Thank  you for your reply.. I removed exclamation mark in front of the timeout warning for below files on one of the APP server and restarted the services

primary-web3.cfg
primary-web2.cfg
primary-web5.cfg
primary-web4.cfg

and waited for 85 mins to get the warning message but i did not received the warning timeout message but instead recevied direct session timeout.

could you let me know if any thing is missing.

What release/patch levels are in question here Subbarao?

thx

_R

Are you using a load balancer? If you are and session persistence is not configured then that could cause the error message you see. We have session persistence set to 10 hours in our load balancer and timeout set to 120 min in the web.cfg files. Sessions exist only on one server so if the load balancer redirects after an hour the user would see the ‘server restarted’ error.