I should add that some loading requests take an excessive amount of time
(20+ seconds) but do not time out. Those are the ones that result in the
unneeded front-end instances shown above.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java"
How are you deploying your classes? Under WEB-INF/classes, or as a custom
JAR file?
Another developer posted that they had a massive performance improvement
deploying their classes in a JAR file - see
https://groups.google.com/d/msg/google-appengine/Gl7OaMOHJD8/i_ti0KceockJ
for the relevant t
We've get the same issue today on our app engine application.
Currently we can see a lot of DeadlineExceededExceptions during the startup
of app engine instances.
Is there any news on how to resolve it?
--
You received this message because you are subscribed to the Google Groups
"Google App
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
We are using a custom JAR but we see the exceptions.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/2Z6-oNjyP_sJ.
To post to this gr
On 31/08/2011 19:48, Simon Knott wrote:
Another developer posted that they had a massive performance
improvement deploying their classes in a JAR file - see
https://groups.google.com/d/msg/google-appengine/Gl7OaMOHJD8/i_ti0KceockJ
for the relevant thread.
A ha!!! I have not tested as a jar
I've tried to jar all the classes from WEB-INF/classes folder, but the
exceptions still there. For now I've come to the situation where I have no
instances up and running because even one instance cannot start.
--
You received this message because you are subscribed to the Google Groups
"Googl
Are you using spring or similar IOC container based framework?-- Sent from my HP TouchPadOn Sep 5, 2011 12:56 PM, Eugene Goncharov wrote: I've tried to jar all the classes from WEB-INF/classes folder, but the exceptions still there. For now I've come to the situation where I have no instances up a
It is possible that you are running into deadlocks when you set
threadsafe=true. As of a few days ago you should begin seeing stack
traces in your logs if we detect a deadlock at the end of a request.
On Fri, Sep 9, 2011 at 10:26 AM, Nick Rudnik wrote:
> I see the same behavior on warmup request
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 have started getting deadlock exceptions thrown from code that uses Guavas
ConcurrentHashMap
http://code.google.com/p/googleappengine/issues/detail?id=5384
Aside from this problem, loading requests frequently seem to block on
something (resource access?). Normally they complete in 5-8 second
Hi Googlers, I was wondering if someone could answer the 3 questions below
regarding slow resource file loading. I am getting a bit tired
of jarring up all classes and resource files (and removing WEB-INF/classes)
every time I want to update my app with GEP.
On Wednesday, 31 August 2011 20:15:
12 matches
Mail list logo
