For some reason, your request is exceeding the request deadline. Note how
ms=100065 60 seconds.
On Thursday, 8 March 2012 21:53:00 UTC+11, Bart Thate wrote:
1.
Hi GAE crew !
1.
2. 012-03-08 11:43:35.845 /dispatch 500 100064ms 0kb Mozilla/5.0
(X11; Linux x86_64)
So how can i diagnose what the reason is ?
On Thu, Mar 8, 2012 at 12:19 PM, Anand Mistry amis...@google.com wrote:
For some reason, your request is exceeding the request deadline. Note how
ms=100065 60 seconds.
On Thursday, 8 March 2012 21:53:00 UTC+11, Bart Thate wrote:
1.
Hi
I am also seeing this and have found no other way to contact the App Engine
team as noted. I've added myself to an issue, commenting and starring it,
but no response over there either.
Just now in the logs from aprigoninjadev.appspot.com
2011-02-14 08:36:39.916
A serious problem was
My jsp are quite simple too, and I've the same issue...
11-15 02:29PM 55.213 / 500 10097ms 0cpu_ms 0kb Mozilla/5.0 (Windows;
U; Windows NT 6.1; en-US) AppleWebKit/534.12 (KHTML, like Gecko)
Chrome/9.0.576.0 Safari/534.12,gzip(gfe),gzip(gfe)
78.233.233.13 - vincent.legendre [15/Nov/2010:14:30:05
Indeed... it was infinitive loop because of our error in algorithm.
With no answer and no support from AppEngine team we have to big doubt
in app engine, so that we overlook our mistakes.
There wasn't possible to log anything or catch exception when this
error happened so we couldn't know if it
Hi Matija,
I'm not using java on app engine, but I can offer the following
- the ms count on the two variations is hugely different - one is less
than a second, and one is over 40s - if commenting out those lines
causes such a difference, then I don't think it is inside this
function that the
my mistake - I can see where you define the 'sequence' array - I'm
just blind - other observations stand :)
On Oct 26, 11:26 pm, hawkett hawk...@gmail.com wrote:
Hi Matija,
I'm not using java on app engine, but I can offer the following
- the ms count on the two variations is hugely
I have the same problem. Any updates on this?
On 22 mei, 01:17, skk shantanu.ka...@gmail.com wrote:
O - one other thing - I can repeat this at will - this is a
repeatable issue.
-skk
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To
O - one other thing - I can repeat this at will - this is a
repeatable issue.
-skk
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send
Make sure the object is serializable. The local dev server wont complain but
production server will. And yes, it will raise the error on retrieval and
not when you store it.
On Mon, May 3, 2010 at 4:55 PM, Peter Warren pe...@nomad.org wrote:
Also, two sidenotes: 1) app engine doesn't complain
The object is definitely serializable. I have several other objects
of the same type in the hash map that work fine. Also, it seems tied
to object size. I can delete some of the xml data that is used in
constructing the problematic object, and it then works fine.
Is there other info I can
Also, two sidenotes: 1) app engine doesn't complain when I put the
object into the HashMap, only when I try to retrieve it. 2) My
application works perfectly when I run it locally in the Eclipse
Plugin environment.
--
You received this message because you are subscribed to the Google Groups
12 matches
Mail list logo
