How could I configure relogin interval?
Accepted answer
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
Comments
One other answer
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.
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.