Hi all,

We are having trouble transitioning from an old version of the code (v15) 
to a newer version (v17). If a user is logged in (we use our own User 
model, not one provided by GAE) to v15, and when we make v17 the default 
version, the logged in user gets Internal Server 500 error when they try to 
access our website. If the user is not logged in, then this issue does not 
exist when we transit to v17.

We noticed that the issue has something to do with the jsessionid cookie 
which gets created and updated when user logs into our website. We know 
this because if we delete this cookie (when a user is logged in) and change 
it to v17, the error 500 doesn't appear. So something is crashing 
internally when it tries to bring back the session information from the old 
cookie that was created through v15. And this problem disappears when the 
user is logged out: so the problem only exists for users who are logged in 
through v15 (so when they come back they go straight to the logged in 
state) and gets exposed to v17 while the session cookie captures their 
logged in state.

It's a hard problem to solve (and we've been spending weeks on this) 
because nothing gets logged on GAE admin console, and we couldn't reproduce 
the problem in localhost (i.e., switching back and forth between different 
versions that we get from our SVN server). There's no information that is 
useful for us to see what might be causing this to happen, and this issue 
is stopping us from going to the updated version of the website.

Has anyone ever encountered this kind of problem, and figured out 
workarounds?

Any kind of help would be much appreciated.


Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to