posted 22 years ago
Which version of WebSphere are you using? I think one of the versions in 3.5 had a bug where this would happen (i.e., it ignored the value you set with HttpSession.setMaxInactiveInterval().
Also, in WebSphere you can set the inactive interval to be something different than the default 30 minutes. Start the WebSphere Admin console, select the Web Application, then select the 'Advanced' tab. Halfway down the page, you will find a 'Session Timeout' property. You can set a specific value here, then tune it without having to change your code.
Final thought. Make sure you are not calling HttpSession.invalidate(). That would clear your session and also the inactive interval you might have previously set.