First, make sure you're using the latest code from CVS.  I think I remember some bugfixes in this area were checked in over the last few months, although I can't recall the details.
If that doesn't fix it, try using SessionMemoryStore instead of SessionDynamicStore.  It's simpler and perhaps doesn't suffer from whatever bug is causing this in SessionDynamicStore, if that's where the bug is.  You can still stop and start WebKit and maintain all session data when using the Memory store (it pickles all sessions when stopping the server and unpickles them all when starting the server).
I have no idea why redirecting would cause this to happen.
Let us know what you find out.
- Geoff
-----Original Message-----
From: JD Kaplan []
Sent: Monday, October 18, 2004 4:29 PM
Subject: RE: [Webware-discuss] session strangeness

Additional information that is pertinent:  I am doing a response.sendRedirect() in the same situation and it turns out that I only get that error if I bounce the server AFTER having done a redirect...





From: [] On Behalf Of JD Kaplan
Sent: Monday, October 18, 2004 3:06 PM
Subject: [Webware-discuss] session strangeness


So I've recently been forced to store some information in the session and I used the transaction.session().setValue() call to do so.  I manage the lifecycle of that information, removing it when I don't need it any longer and putting it in only when I need it.  The code works fine and I'm happy about that.  The bad thing is that if the server goes up and down for any reason I get this error:



Traceback (most recent call last):
  File "WebKit/", line 395, in dispatchRequest
  File "WebKit/", line 494, in isSessionIdProblematic
  File "WebKit/", line 222, in session
  File "WebKit/", line 67, in session
  File "WebKit/", line 963, in createSessionForTransaction
  File "WebKit/", line 789, in session
  File "WebKit/", line 72, in __getitem__
  File "WebKit/", line 135, in MovetoMemory
  File "WebKit/", line 55, in __getitem__
KeyError: '20041018134147-bb1e0e08b042e0a050094e719c7b8ab8'
I can fix this by manually clearing the cookies in my browser, but that's a pain in the butt that I'd like to not foist upon the people using the web architecture to develop page content.  Can anyone shed some light on whats going on here and why?  
My server is set to use dynamic sessions at the moment.



When I grow up, I want to be the lesser of two evils.