I switched back to true , upgraded to SDK 1.5.2
and for a week the number of deadlocks seems to be greatly reduced.
I do still get deadlocks but now the error reporting is MUCH better. They
normally occur in some Google generated method
com.google.appengine.runtime.Request.process-XXX.
Of
Ikai, I have created a new topic explaining more in detail my problem.
Can you help me please, or address me to the right people who can help me on
this?
This is the topic I sent:
"since last week I am experiencing a very serious problem in my application.
Probably since I deployed for the fi
Thanks Ikai, I'll open a new thread with this to see if anyone experienced
this problem.
--
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-ja
Eduardo, it sounds like you're encountering a different problem than John.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine
On Tue, Jul 26, 2011 at 7:33 AM, Eduardo
Ikai, regarding the fix pointed out by you, '*setting "threadsafe" to false*',
well it delays a little the appearance of the problem, but after some time
it arises again.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view th
Hi,
I have been experiencing locks with task queues since last week too,
specially when I use dynamic instances in my backends. During minutes the
CPU load goes to 0% on all instances, and the queues keep growing but no
single task is executed (and this happens with as few tasks as 10). After
On Tuesday, 26 July 2011 04:03:44 UTC+7, Ikai L (Google) wrote:
>
> John, yeah, it's a deadlock, possibly in userspace code. Can you look into
> this?
>
>
The only pattern I could detect was the dead-lock with concurrent file
access - I had my web framework in dev mode so each request was loadi
John, yeah, it's a deadlock, possibly in userspace code. Can you look into
this?
On our end we'll see if we can surface and more usable error message.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: h
In case others are facing these time-outs, by setting "threadsafe" to false,
all errors stopped and response time does not seem significantly different.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on th
Oh also, I was previously getting deadlocks ( time-out without exception) as
more than one thread tried to read a resource from the file system.
I wonder if the wide variety of circumstances that this problem occurs in
points to something fundamental like the security manager?
--
You received
Ikai, do you know if this deadlock issue is a recent problem? I want to
figure out if any recent changes I've made could be accentuating it.
--
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
Thanks Ikai, its great to know you guys are onto it.
http://code.google.com/p/googleappengine/issues/detail?id=5384
I am also seeing time-outs with out in my front end requests. I ran the
tasks from a different app version to run on different instances just to be
sure that tasks were not taki
Okay, there's a bug here related to deadlocks. Can you file an issue in the
issues tracker and post it to this thread? I'll link the issue with our
internal issue so it receives updates when we address it.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspo
I don't believe this is related to memory. Do you know what you are doing in
this task?
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine
On Wed, Jul 20, 2011 at 6:56
I have a task which sometimes runs fine in a few seconds and other times
locks up and times out after 10 mins. The logs do not show any exception
just this message:
2011-07-21 01:38:06.983
A serious problem was encountered with the process that handled this request,
causing it to exit. This i
15 matches
Mail list logo