You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/03/29 20:01:22 UTC
DO NOT REPLY [Bug 7613] New: -
session timeout setting ignored/confusing to configure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7613>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7613
session timeout setting ignored/confusing to configure
Summary: session timeout setting ignored/confusing to configure
Product: Tomcat 4
Version: Nightly Build
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: dlr@finemaltcoding.com
StandardManager's maxInactiveInterval is ignored in my Catalina setup with the
20020124 HEAD nightly. build
<context ...>
...
<Manager maxInactiveInterval="2" debug="1"/>
</context>
StandardContext's sessionTimeout is also ignored:
<context sessionTimeout="2" ...>
...
</context>
I have only had success with setting the session timeout in the web application
deployment descriptor:
<session-config>
<session-timeout>2</session-timeout>
</session-config>
Also, I couldn't tell which of these 3 ways was the recommended method for
setting a session timeout (assuming that all three actually do just that). It
looks like some are used as overrides and other as baselines, but the
documentation was nearly non-existant. If someone can clarify this for me, I'll
submit the appropriate xdoc changes.
Note that I have custom Valve implementations that manipulate Sessions using the
Catalina API. However, since the session-config/session-timeout property works
for me, I'd be hesitant to say that this custom Valve is affecting things.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>