This is an update to my earlier email.
Problem: setting session timeouts in 4.1.x's server.xml is pointless.
Why: setting the Manager's attribute "maxInactiveInterval" or
Contexts's attribute "sessionTimeout" is pointless because they get
overwritten by the session timeout in the web.xml or if
Problem: setting the "maxInactiveInterval" on the Manager tag
doesn't work.
Why, well the problem is that two objects think they own the same
information. Namely, the Context and the session Manager both claim to
own the SessionTimeout.
Each object has these properties.
Manager.maxInactiveI
