Hi, Kenny.
I think this is basically how it works:
- Tomcat's conf web.xml sets the default session-timeout (in
session-config element) to use for all web apps.
- You can specify a different session-timeout in each specific web app you
deploy in the web app's WEB-INF/web.xml file.
- This session timeout can still be overridden in application code using
the session.setMaxInactiveInterval method.
I hope this helps you find the problem.
-Jeff
"Kenny G. Dubuisson, Jr." <[EMAIL PROTECTED]>
12/20/02 09:05 AM
Please respond to "Tomcat Users List"
To: "Tomcat Users List" <[EMAIL PROTECTED]>
cc:
Subject: Re: Session timeout setting (URGENT)
Simple minded as I am, I still believe with everything I have that there
MUST be a setting in Tomcat that controls how often new session ID's are
generated. If I have a simple page that does nothing but a
"session.getId()" and it returns a new session ID every 60 mins, there
must
be something in Tomcat that sets this interval. Obviously this setting is
missing from my config files so that Tomcat uses it's default. Has no one
ever wanted to change this setting before? I hate to sound beligerent but
I've authored and released what I feel to be a very nice application/web
site but the only feedback I'm getting is litterally users screaming at me
because I haven't fixed this yet. I'm going to have to start looking at
redesigning the login/verification process on every page (not a big site
but
still 20K of code) to work around this issue when I feel it has to be a
simple setting.
If someone could answer this I'll give you my first born, send expensive
Christmas presents, lend you my wife. Thanking / Praising you in advance,
Kenny
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
