tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Herrmann <...@jadn.com>
Subject SessionTimeout Problem
Date Wed, 26 Jun 2002 20:12:50 GMT

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.maxInactiveInterval is the session timeout in "seconds"

Context.sessionTimeout is timeout in "minutes"


The digester creates a Manager (and may correctly set it's
maxInactiveInterval) and then binds it to a Container (Context.)  The
Context overwrites the Manager's maxInactiveInterval with it's own
sessionTimeout.  

Once bound to a container, the Manager watches the sessionTimeout
property changes and adjusts its own maxInactiveInterval value to
track it (Useful when the web.xml is processed and the digester updates
the Context's sessionTimeout)

Not sure how to correctly proceed.  The Manager isn't bound to 
a container when it's maxInactiveInterval is set by the digester,
so it cant tell the Context to use its value. 

Any ideas?

Cheers
-bob



--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message