well... i tried that, but could not get it to work.  i did a quick test 
by   making  session.invalidationtime=3 in the global.properties and 
setting the session timeout=5 in the web.xml.  When I did this, it 
worked.  However, I did these tests rather hastily - I'll try again now.

At 03:50 PM 08/14/2001 -0400, you wrote:
>Hi Tom,
>
>If you set it in the global.properties and you have the same entry in
>local.properties for the server instance or if you have the same entry in
>the web.xml for the application, the latter will take effect no matter what
>you set in the golbal.properties.
>
>Thanks,
>
>Bin Zhou
>
>
>
>
> >From: Tom Duffy <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: JRun-Talk <[EMAIL PROTECTED]>
> >Subject: RE: session timeout [correction]
> >Date: Tue, 14 Aug 2001 15:44:23 -0400
> >
> >Hello Scott,
> >       I have been having trouble managing a sessions timeout and in my 
> research
> >I came across a discussion you had win Bin Zhou on this matter.  I think
> >you may have solved my problem already, but I would like to confirm
> >somethings with you (if you don't mind).
> >
> >I have set my session timeout values to as low as 3 minutes, but still
> >cannot get the session to timeout.  I run the app, login, enter data into a
> >form and then begin my timer.  After 3 min (lets say at 5 min) I hit the
> >submit button, but the session appears to still be active and did not
> >expire as I expected.
> >
> >(Is the test I described above valid for checking if a session has
> >expired?)
> >
> >In your response to Bin, you stated "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."
> >
> >I see the following in the global.properties file:
> >
> ># Invalidation time is the default session inactivity timeout.
> ># If the session is not accessed, it will be expired.  This value
> ># can be set on each session by calling HttpSession.setMaxInactiveTime()
> ># specified in minutes.
> >session.invalidationtime=30
> >
> >I see that the session.invalidationtime=30.  I assume this is 30 minutes.
> >If this is correct, then I would not get my session to invalidate until 30
> >minutes have passed.  Is this correct - the session, although it has
> >exceeded it 3 min idle time, will not get invalidated (killed) until the
> >session.invalidationtime has come to reap it?
> >
> >Please confirm, as the description above (provided with the default
> >global.properties file) is not clear on this matter.
> >
> >Also, can the session.invalidationtime property be set in the local
> >properties for a server?
> >
> >thanks in advance!
> >
> >Regards,
> >
> >Tom Duffy
> >
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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

Reply via email to