Web and Eclipse timeout
Accepted answer
<session-config>
<session-timeout>360</session-timeout>
</session-config>
Comments
Jared,
Is there a different area for eclipse clients?
Because the timeout is defined in the deployment descriptor, it's down to the application server (Tomcat/WAS) to expire the session after the timeout has elapsed. Seeing as the eclipse client just connects over HTTP it should be affected as much as your browser window is.
The only thing that could cause a difference between the eclipse and web-clients is if the eclipse client were to make any sort of periodic background request to the server. If it were to do this, the server might reset the countdown on the timeout.
Many thanks Jared
Hi Jared,
I tried to change session timeout to 30 minutes. Modified web.xml deployment descriptor of jts and ccm accordingly:
<session-config>
<session-timeout>30</session-timeout>
</session-config>
However, the session does not timeout after idle 30+ minutes after no activity from /jts/admin web UI- no pop up window asking for login.
Another web.xml- install_dir/server/tomcat/conf/web.xml also has timeout set to 30 minutes(by default):
<session-config>
<session-timeout>30</session-timeout>
</session-config>
Tomcat restarted after above changes.
Did I miss anything?
RTC 4.0.0.1 + Tomcat 7.
Just to update that this change (Modified web.xml deployment descriptor) works. Possible in my first test, the restart of Tomcat did not pick up the changes properly.
Where is this web.xml when using WebSphere?