I'm getting this same error after enabling async-session-persistence,
except 100% of the time. It shows this error in the logs:
javax.servlet.ServletContext log: _ah_queue_deferred: Deferred task
failed exception:
com.google.apphosting.utils.servlet.DeferredTaskServlet
$DeferredTaskException:
I'm quite unhappy about the new pricing. The pay per usage model
was the main reason I chose GAE. On the old model, I could handle a
reasonable amount of traffic with just paying $9/month for getting 3
reserved instances. Letting my users get loading requests is bad
since my loading requests
If you use the user's api then in all the logs it shows the user's
username right after the ip address in the log entry. My app doesn't
use the user's api, it just uses it's own user management with the
datastore.
Is there a way that I can get the user's username, or alternatively,
datastore id
I get:
javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No name matching
appengine.google.com found
Unable to update app: java.security.cert.CertificateException: No name
matching appengine.google.com found
when trying to update my app.
It just started this morning.
reloaded, I have a static class variable
that if it loses its value I assume we are starting again. Is that
logic sound? or do I need this SessionListener the reference talks
about?
My way seems even simpler if it works.
Thanks
Steve
On Mar 20, 10:19 pm, Spines kwste...@gmail.com wrote
Well, I figured it out, I just deleted all of the jars I didn't need
from my ./build directory. I deleted all of the JDO, JPA, and
datanucleus jars. The result of doing this was I got my first cold
start that happened under 1200ms :). Previously the CPU time used by
a cold start was pretty
I definitely want async datastore operations.
Looks like there is an issue in the issue tracker now -
http://code.google.com/p/googleappengine/issues/detail?id=2817
On Feb 14, 8:02 pm, Ivan Pardo trux...@gmail.com wrote:
async datastore operations would be incredibly useful
On Jan 23, 1:09
I'm interested in the asynchronous datastore commands. How does it
work behind the scenes? I'm using the low level datastore API and
think asynchronous writes could be really useful for my project. I
browsed through the low level api docs, but couldn't find a way to do
an asynchronous command.
it won't work, it just means no one has tried it.
Can you try it and let us know so we can update the page?
On Thu, Mar 11, 2010 at 8:44 PM, Spines kwste...@gmail.com wrote:
I think bouncy castle is a good library to use, does anyone know if it
works on the app engine?
--
You received
I'm only able to delete 20 entities at a time, I have over 500
entities of a certain kind. Is there a way I can delete them all from
the admin console?
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send
Anyone know of a reliable Java library for cryptography that works on
the app engine? I want to encrypt with AES.
--
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
I think bouncy castle is a good library to use, does anyone know if it
works on the app engine?
--
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 google-appengine-j...@googlegroups.com.
To
Where does Google store the logs when you do a Logging statement?
Logging statements seem to be pretty fast, so it doesn't seem like
they are stored in the datastore.
How reliable are the logs? If I do a logging statement and it
succeeds, is it pretty much guaranteed that it will show up in the
Yea, it seems that according to Eduardo's link the jsps are
precompiled, so it is probably something else.
On Feb 14, 8:45 am, Eduardo Ramírez edu.ky...@gmail.com wrote:
On Sun, Feb 14, 2010 at 17:05, Brian Wawok bwa...@gmail.com wrote:
**
**
*I suspect precompile only hits .java files and
mystery pause.Something to do
with setting up datastore I guess.. but very annoying.
I want to love google app engine, but it feels so far from product ready...
On Sun, Feb 14, 2010 at 1:04 PM, Spines kwste...@gmail.com wrote:
Yea, it seems that according to Eduardo's link the jsps
(ie your traffic load goes up).
On Feb 14, 5:24 pm, Spines kwste...@gmail.com wrote:
Yes, that database lag you talk about is JDO setting up the metadata
for objects. If you go into your logging.properties and change the
logging level to FINE, you can see what it is doing.
On Feb 14, 11:26
will see on that...
On Feb 12, 6:27 pm, Spines kwste...@gmail.com wrote:
Anyone know?
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from
By the way, what I am talking about above is an experiment I did to
see if a simple jsp experienced this. I first noticed it in my real
app which has a loading request time of about 7 seconds due to using
Spring MVC and other things. On my real app I noticed that even after
the loading request
The first access to a jsp page takes a while. A simple hello world
takes about 600ms of cpu time. This is not due to it being a loading
request. I have a servlet that doesn't use jsp, and I hit that first
to do the loading request, then I hit the jsp and it takes ~600ms to
respond. Subsequent
Hi,
I have an alternative for getting Spring forms working on the app
engine. Instead of registering custom editors for your properties,
you can just comment out the offending line (a call to
findEditorByConvention) in the spring source code and recompile.
Everything will work fine as long your
I get a deadlock on the development server. It happens about once
every 4 times I startup my app. It happens at PMF.clinit:11 the
first time I access my PMF class, which is just a copy paste of the
example PMF class from
http://code.google.com/appengine/docs/java/datastore/overview.html.
Deeper
Great! I can definitely initialize synchronously. I was just worried
that there may be an issue with my code that would only show up
sporadically on the production app engine.
On Feb 10, 1:35 pm, Don Schwarz schwa...@google.com wrote:
On Wed, Feb 10, 2010 at 3:09 PM, Spines kwste...@gmail.com
I get an InvocationTargetException the first time I query the
datastore after starting the dev server.
My app works fine, but I feel like the exception slows down the
startup time and is also probably a bad thing.
My query is simple its just:
Query q = pm.newQuery(Question.class);
ListQuestion
23 matches
Mail list logo
