I am having an intermittent problem with session expiration handling.
First, my background specs. WSAD 5.1.1 Windows XP Pro using WSAD testing server using a DB2 backend using jcc DB2 driver
Here is my scenario which happens maybe 5% of the time: I log in to my webapp. I let the session expire. When I click on a link, it goes to my error screen and tells me the session is expired. So, I go back to the login(html) page which posts to the LoginVerification servlet. When it gets to line 305(lines 304 and 305 are below for reference), I get the following(labelled First Error below) in my console window. Upon seeing this, I type the url for my login page again and try to log in again. This action produces another error in my console window, labelled Second Error below. I then must restart the test server because the JVM core dumps.
Any ideas? I would hate to have this happen when the application goes live.
=========================================== First Error
====================================================== Second Error
[edited to disable smilies] [ August 04, 2004: Message edited by: Jeanne Boyarsky ]
Jason R. Kretzer<br />Software Engineer<br />System Administrator<br /><a href="http://alia.iwarp.com" target="_blank" rel="nofollow">http://alia.iwarp.com</a>
posted 11 years ago
I think that cheeky little smiley's munched your connect string!