Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How could I configure relogin interval?

 Hi, we are using RTC3.0.1.3, and as we know, after logging in to RTC in web browser,  if we have a period of time not in use, we will be asked to log in again.

My question is: Is there any way to configure the log in timeout period? and How?

1 vote


Accepted answer

Permanent link
 This is determined by the session-timeout value in the deployment descriptor for your application.

If you're running on Tomcat you can edit the web.xml file directly:

<session-config>
    <session-timeout>15</session-timeout>
</session-config>
 If you're running on WAS then the setting needs to be set through the console - the following looks like the right field:

Applications -> WebSphere enterprise applications -> <application> -> Session management -> Session timeout
Di Tang selected this answer as the correct answer

3 votes

Comments
Thank you for your reply and I already found the setting you said. But I have a furthur question, Is that mean the timeout period only determined by my tomcat/WAS?

That's my understanding, yes. With regards to your other question about license & token timeout, this refers to the amount of time a license is assigned to a user.


E.g. if your session timeout is 60 mins and the license timeout is 30 mins, potentially a user could go away for 45 mins and still be logged into the tool but might no longer have a license if all of the licenses are now in use.

Jared, thanks for that answer, the default of 6 hours tells me why I never see the session timeout happening.

With respect to the license timeout, the default is 120 minutes for floating licenses, and I think you are not supposed to change it, because it might violate the license agreement.

Jared and Ralph, thanks for your answer. I think Jared's answer is right and I will do some test later.


One other answer

Permanent link
Hi,

I have read this some times in the forum. If I use Jazz.net, I don't have to login, neither do I have to with all my test systems on my machine - ever. I have discussed this with several people and got several hints why this could be happening to people. Most of the hints were about infrastructure related settings that are company/site specific.

  • There is infrastructure around that can and do drop connections after some idle time
  • Other settings could probably cause this as well, such as application server settings
  • We have seen issues with LTPA timeouts when running performace tests against IHS/WAS, where you can change the LTPA timeout. I have been told, that the timeout should not affect a regular user.  

So, I am not aware of a timeout in Jazz that would force logging in again. If anyone knows any that I have been missing, please correct me. I would rather check with the infrastructure teams,if there are settings that could cause this.

0 votes

Comments

Hi, Ralph, thank you for your reply!

I found there are some setting about license timeout and token timeout, but I'm not sure those setting affect it or not.

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 6,118
× 30
× 11

Question asked: Feb 27 '13, 3:10 a.m.

Question was seen: 6,961 times

Last updated: Feb 27 '13, 8:23 p.m.

Confirmation Cancel Confirm