I have asynchronous sessions enabled in my java app and constantly see this in
my logs. It appears that the deferred task to write the session data to the
datastore is failing because of a missing class. Is the production runtime
missing this class or is there something I need to include in my
I don't see anything that indicates a deadlock. In the logs, I just see
normal deadline exceeded exceptions and stack traces of where it happened to
be when it was cut off. I don't believe I've ever seen a log message with
the deadlock situation.
I thought the explanation might be that non-load
I see the same behavior on warmup requests but only when threadsafe=true. If
I leave threadsafe set to false, my warmup requests never have deadline
exceeded errors. This is very troubling because we really need
threadsafe=true in light of the new pricing.
I can't find a good explanation for t
I'm not sure it's supposed to be that way but I can confirm I see the same
behavior. I can reproduce it in a Junit test case when using
the LocalServiceTestHelper but only when using the low level java api, not
JDO. Which API are you using?
--
You received this message because you are subscri
It will only clear when the execution succeeds. Check your log to see why it
failed. Make sure your cron job actually returns a clean response with the
http 200 code.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to th
Why would this be needed? The session implementation stores its data outside
of a specific jvm so every instance has access to all sessions. It is a very
excellent design decision not to have to connect a user to a single instance
for the life of a session. Instances can come and go as they plea
You found the right article. Simply, you have to create a POJO with the
proper annotations for the fields you want to persist, instatiate the POJO
and set the properties with your two values, get a reference to the
PersistenceManager and save the POJO.
--
You received this message because you
It sounds like you need a keyOfA in class B with the extension annotation so
A B and C all end up in the same entity group. If you are actually only
updating B and C together in a transaction, the extension annotation should
only be necessary on the keyOfB member in class C.
There is also some
If I understand correctly, are you trying to POST from within the servlet
code? If so, there are restrictions on the way you are allowed to open a
network connection from within your application. There is a special Google
provided class to make a network connection that way. Maybe that's your
p
The problem is likely that your domain provider is doing a simple redirect
to your www hostname where App Engine is able to respond. The redirect logic
is probably very basic in that it does not preserve the rest of the request
url when doing the redirect. The only way I know around this is to h
Spring MVC 3 works very well inside App Engine. I have a fairly small and
simple application and see a load time of around 20 seconds also.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to goog
You are correct that writing to memcache is by far the cheapest way to save
data. A cron job to periodically persist the changes to the datastore is
required if you care to make sure your data isn't lost. Memcache can be
flushed for any reason at any time. The frequency of the cron job will
det
12 matches
Mail list logo
