It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×7,383
×5,997

question asked: Apr 05 '16, 3:54 p.m.
question was seen: 1,707 times
last updated: Apr 05 '16, 9:04 p.m.

Related questions

FAQ - How this Forum works

For release CLM 5.0.2 our users are experiencing session interruptions

0
Timothy Miller (13●2●14) | asked Apr 05 '16, 3:54 p.m.
Our users are being forced to log back into the application as they are getting kicked out with no warning and or message. Trying to understand if this is a known issue. The WebSphere timoeout setting is at 60 minutes.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ted Mayer (476●4●9) | answered Apr 05 '16, 4:12 p.m.

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

0
permanent link
Donald Nong (14.5k●4●14) | answered Apr 05 '16, 9:04 p.m.
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.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.