Please forgive me -- Bin Zhou was correct and I was not. JRun 2.3.x had a
setting as I described. Bin is right about how 3.x works.
My humble apologies!
Scott Stirling
JRun QA
Macromedia
-----Original Message-----
From: Scott Stirling
To: '[EMAIL PROTECTED]'
Sent: 7/23/01 6:12 PM
Subject: RE: session timeout
Not quite, but partly right.
The web.xml setting sets the valid duration of a user's session, per the
Servlet 2.2 spec. The session.invalidationtime setting is to tell JRun
how often to schedule a sweep of the sessions in memory in order to
invalidate and reap sessions that have expired.
Scott Stirling
JRun QA
Macromedia
> -----Original Message-----
> From: Bin Zhou [mailto:[EMAIL PROTECTED]]
>
> The one in the web.xml file is applied to the specific
> application. The one
> in the global.properties file is applied to all the
> applications in all jrun
> server instances. I guess if you do not specify the one in
> the web.xml, the
> application will use the value in the propertities file as default.
>
> Bin Zhou
>
>
> >From: [EMAIL PROTECTED]
> >
> >
> >What is the difference between the
> <session-timeout>30</session-timeout>
> >parameter in the web.xml file
> >and the session.invalidationtime=30 of the global.properties file
> >
> >brgds Christophe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
