I figured out the source of my confusion about the session expiration. In my testing, everything was working properly. After session expiration, I would get a new session ID and a fresh, clean session on the first request.
It turns out that I was making that request after the session sweeper thread had already purged the session from the session store, in which case everything works properly. If I instead make that request after the session expires, but before it gets purged by the session sweeper, it fails as you've described. It's definitely bad that the behavior depends on whether the session sweeper has run or not. The fix is easy -- I'll just have Application.handleInvalidSession() delete the session from the transaction. I'll test the fix and check it in in a few minutes if it works. - Geoff ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
