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.
[mailto:webware-discuss-admin@...] 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/Application.py", line 395, in dispatchRequest
File "WebKit/Application.py", line 494, in isSessionIdProblematic
File "WebKit/HTTPRequest.py", line 222, in session
File "WebKit/Transaction.py", line 67, in session
File "WebKit/Application.py", line 963, in createSessionForTransaction
File "WebKit/Application.py", line 789, in session
File "WebKit/SessionDynamicStore.py", line 72, in __getitem__
File "WebKit/SessionDynamicStore.py", line 135, in MovetoMemory
File "WebKit/SessionFileStore.py", line 55, in __getitem__
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.