I found something. Maybe not significant but could be. I saw in the log that
two of the last sign ins that failed had a call to /_ah/warmup just prior to
them. With the log text:
This request caused a new process to be started for your application, and thus
caused your application code to be
You're not placing anything in your session which isn't serializable are
you?
Given that everything seems to be failing when it's starting up a new
instance, which is when it will attempt to read the session out of the
datastore/memcache, it may be that it can't deserialize your data.
--
have you tried viewing the http headers in each request
using chrome, firebug, httpwatch, etc?
sunshine is the best disinfectant
I dont think redirects normally can set cookies
maybe the prod server is striping your
invalid host headers on a redirect
On Aug 28, 7:32 am, Simon Knott
Following is the solution I am planning to implement for a similar case in
my application. But, it depends on your data.
*Method 1*
* Create 3-4 additional properties in the BOOK kind. Like for example,
word1, word2, word3 properties etc.
* Split the book title into words and store each word
The object put into the session is serializable. The production server will
throw an exception if the session is attempted to be set with a
non-serializable object.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
I haven't checked the http headers yet. The tricky thing is that it usually
works fine even on the production server! It could be that I set the cookie
in a non-standard way, but the session attribute is that a cookie too (I
don't know fully how GAE manages sessions)?
On Sunday, August 28,
You should read on list properties. This will allow you to store
keywords into a single property and search on them. You could manually
split your strings bu instead you can use an Analyser from Lucene or
Hibernate Search. The analyzer can be used without really using Lucene
or Hibernate.
You
I noticed that when the sign in doesn't work the redirect goes to / the
root. I have looked and looked for where this can happen in the code, but
there is no place where the redirect can be / (unless I have missed finding
it in the code). Can the sendRedirect() sometimes cause a redirect to /
