Could the sample app that you're using use the WebSession and the one
that Todd is testing use the SimpleSession?
Regards,
Alan
On Nov 11, 2008, at 11:50 AM, Les Hazlewood wrote:
Hi Todd,
Sorry about the late reply - I've been out of town until yesterday.
The session expiration time is calculated based on the session's last
access timestamp. This timestamp is updated during almost all
operations to a session, so it should be calculated correctly. Are
you still seeing this?
The sample applications I've tested (after building JSecurity) work as
expected - I can click a link every 15 minutes or so over an hour, and
my session isn't timing out. I'm confused as to how this is happening
for you. Do you have any other information?
Cheers,
Les
On Thu, Oct 30, 2008 at 12:16 PM, Kofford, C Todd <[EMAIL PROTECTED]>
wrote:
I'm using jsecurity RC2, and I keep seeing the session for my webapp
expire after 30 minutes. Even though I do reads and writes to the
session, it unconditionally expires after 30 minutes.
Is this by design, or should session access (read or write) delay
session expiration for another 30 minutes?
Thanks,
Todd Kofford
[EMAIL PROTECTED]
University of Kansas - IT
