You could use the session instance method setMaxInactiveInterval which takes a single int paramter which is the maximum time in seconds between client requests before invalidation.

For example, for ten minute timeout:

session.setMaxInactiveInterval(600);


-Mike Fowler "I could be a genius if I just put my mind to it, and I, I could do anything, if only I could get 'round to it"

Tim Funk wrote:
The session timeout can be changed at runtime (sort of). If you change web.xml - you would need to restart your webapp. This would cause a brief outage while sessions are saved to ???. (Unless your using clustering)

If you really need this changed on the fly, this might be able to be changed via JMX. (But I haven't checked)

-Tim

Arun Prasad R wrote:

hi

in web.xml the following comment has been given
<!-- You can set the default session timeout (in minutes) for all newly -->
<!-- created sessions by modifying the value below. -->


    <session-config>
        <session-timeout>30</session-timeout>
    </session-config>

after changing session-timeout will it be effective for sessions
created thereafter?


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to