Tomcat not timing out sessions

[Ryan Rank]

I saw a couple similar threads, but nothing with a solution or didn't quite fit. If there is a thread with a solution, please point me to it.

I am working with a vendor supplied application (which I do not have access to the source code for) where the timeout settings are set to 30 minutes. The context web.xml file has the timeout setting at 30 minutes, and the /conf/web.xml has it set to 30 minutes as well. Idle sessions are sitting out there for hours on end until the heap runs out of memory and starts to dump. My only way out of this is to restart Tomcat.

Tomcat version 4.1.40
JRE is IBM 1.4.2

The vendor's support of Tomcat is a bit spotty; I'm starting to get a bit desperate.

Any input for this would be appreciated.

[Tim Holloway]

Well, you're using an end-of-life'd version of Tomcat, so you've got potential trouble right there.

But as far as timeouts go, the web.xml definition should be authoritative, regardless of which version of Tomcat and whose JVM you're using. I suspect that there's something internal to the app that takes action when it detects a timeout. Hopefully the vendor can clue you in.

[Ryan Rank]

Back to the vendor's court it is. Thanks for the assist!