-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
>> I've been using JSDK 2.1 and its provided web server and using
>> HttpSession to store objects for a users session in a servlet. Now, in
>> JSDK2.1 there is the HttpSession setMaxInactiveTime() method so you
>> can set the duration of a 'session'. I'm now using JSDK 2.0 with JServ
>> 1.0 and Apache 1.3.6 on Solaris. Such a method is not available in the
>> JSDK, but is it available with Apache ? or som other way ?
>> How do I get the same effect of keeping sessions active for long
>> periods ?
> Apache doesn't know anything about servlet sessions, so you won't find any
> help there.
> The setMaxInactiveInterval() was added in the 2.1 version of the servlet
> API, which Apache JServ 1.0 does not support. However, you can set the
> session timeout for all created sessions in the zone properties file,
> using property "session.timeout". The value is expressed in
> milliseconds.
Thanks. I've now found that one (and it helps a lot). Actually maybe I have
been misunderstanding the problem. What I actually have are 2 servlet
zones. One zone has a servlet com.wdr.FTB.FTBServlet which many users are
using. I have a second zone which I am using for development of the same
com.wdr.FTB.FTBServlet. When I swap between the 2 servlets, I have to log
back in (i.e new HttpSession) each time. Is it to be expected that I can
have a servlet of the same name in JServ via a different zone and retain
HttpSession's ? (or does JServ unload whichever version is loaded, when the
other one is called ?)
TIA
--
Andy
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
