For release CLM 5.0.2 our users are experiencing session interruptions
2 answers
Are your users timing out prior to 60 minutes?
This configuration change is not performed on the application side but rather at the Tomcat or Websphere application server side. The following article below will have instructions to configure the timeout setting:
http://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.0.0/com.ibm.websphere.base.doc/info/aes/ae/tprs_cnfs.html?lang=en
In Websphere Application Server, there is setting called 'No timeout' which can be used to help with the users not having to login again.
Regards,
Ted
If you're using a distributed environment with multiple WAS profiles, it is possible that the SSO has not been configured correctly and such problem can occur. For example, it can happen that whenever a user tries to access QM, he needs to log in, and the existing CCM session will become invalid immediately; and when he comes back to CCM, he needs to log in again, and the QM session becomes invalid; and so on.