[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-11-02 Thread Alexandra 
Hi,

Did you find the reason of these errors?

I also see a lot of them. The time which is elapsed is about 10 min, so it 
seems that there are tasks that are stuck for some reason in the task queue.

Any insights on that?

Thanks
Alexandra

On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>
> "Request was aborted after waiting too long to attempt to service your 
> request."
>
> I've been seeing these messages a lot lately, momentarily many requests 
> log these errors, it floods the error logs
>
> Anyone else?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/aece30e7-9ee5-4f5b-95e2-775e91430eb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-11-02 Thread Nick (Cloud Platform Support) 
Hey Alexandra,

If you're experiencing an issue on the platform, the best way to report 
that issue and get help with it would either be to post on a Stack Exchange 
site (Stack Overflow  for example), in the case 
that you think the issue is related to your own code, or on the public 
issue tracker for App Engine 
, if, having 
followed all documentation and fully understanding the issue could not be 
in your code, you suspect that the issue might be on our side, which we can 
fix. 

Unfortunately, this thread contains next-to-zero useful debugging 
information other than some instance stats (F2 instance) and a vague 
indication that the error coincides with bursts of activity, so this thread 
can't really function as an issue report which is actionable.

So, I wish you or anybody else experiencing issues who reads this thread 
the best of luck in reporting your issue through one of the forms above, 
and hopefully with providing enough information, you can have someone help 
you out with a solution for your code or a tracking number for a solution 
to be patched, depending on the situation.

On Monday, November 2, 2015 at 10:48:57 AM UTC-5, Alexandra wrote:
>
> Hi,
>
> Did you find the reason of these errors?
>
> I also see a lot of them. The time which is elapsed is about 10 min, so it 
> seems that there are tasks that are stuck for some reason in the task queue.
>
> Any insights on that?
>
> Thanks
> Alexandra
>
> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>
>> "Request was aborted after waiting too long to attempt to service your 
>> request."
>>
>> I've been seeing these messages a lot lately, momentarily many requests 
>> log these errors, it floods the error logs
>>
>> Anyone else?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d54b3bd0-396b-48dc-a0f8-32b7168feca3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-11-02 Thread Kaan Soral 
Yes, AppEngine can't handle bursts well, so the solution is to slow things 
down

Actually, there are speed limits on a lot of things that are usually not 
advertised well, if you are getting these kind of errors, try to slow 
things down and see how it goes

Slowing things down is also pretty challenging, much harder than building 
stuff that will scale

On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote:
>
> Hi,
>
> Did you find the reason of these errors?
>
> I also see a lot of them. The time which is elapsed is about 10 min, so it 
> seems that there are tasks that are stuck for some reason in the task queue.
>
> Any insights on that?
>
> Thanks
> Alexandra
>
> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>
>> "Request was aborted after waiting too long to attempt to service your 
>> request."
>>
>> I've been seeing these messages a lot lately, momentarily many requests 
>> log these errors, it floods the error logs
>>
>> Anyone else?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e5949fb2-50fd-41d2-b0f7-7ba5bd441b58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-11-03 Thread Jason Collins 
More min_idle_instances (at an increased cost of course) will help service 
bursts and avoid these pending queue timeouts.


On Monday, 2 November 2015 18:05:30 UTC-8, Kaan Soral wrote:
>
> Yes, AppEngine can't handle bursts well, so the solution is to slow things 
> down
>
> Actually, there are speed limits on a lot of things that are usually not 
> advertised well, if you are getting these kind of errors, try to slow 
> things down and see how it goes
>
> Slowing things down is also pretty challenging, much harder than building 
> stuff that will scale
>
> On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote:
>>
>> Hi,
>>
>> Did you find the reason of these errors?
>>
>> I also see a lot of them. The time which is elapsed is about 10 min, so 
>> it seems that there are tasks that are stuck for some reason in the task 
>> queue.
>>
>> Any insights on that?
>>
>> Thanks
>> Alexandra
>>
>> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>>
>>> "Request was aborted after waiting too long to attempt to service your 
>>> request."
>>>
>>> I've been seeing these messages a lot lately, momentarily many requests 
>>> log these errors, it floods the error logs
>>>
>>> Anyone else?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7b7bca79-e617-4660-bae3-dc0970c6c9e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-11-03 Thread Nick (Cloud Platform Support) 
@Kaan Soral

I think the issue cannot be adequately narrowed-down from the information 
provided, and with only the commonality of seeing the "Request was aborted 
after waiting too long to attempt to service your request." error, it's 
impossible to determine that the same issue is being reported by Alexandra 
- that's the reason why a proper issue report 
 is needed (see in 
that link a template).

There doesn't seem to be a basis for inferring the general statement that 
"AppEngine can't handle bursts well". This is especially so when the 
justification for the statement refers to a very specific use-case related 
to errors seen in a task queue with specific scaling settings. These 
scaling settings might be at the heart of the original issue reported at 
the top of the thread. Having a minimum and maximum of 1 idle instance 
doesn't exactly lend itself to managing every possible burst. 

Depending on the request pattern and start-up time, you could see strange 
scenarios where requests are building up in pending queues, instances are 
firing up and then shutting down after becoming idle, with the pending 
queues migrating and merging among these rapidly spawning and de-spawning 
instances. Requests in a rather short pending queue dealing with this 
potentially-volatile setup would not be seen to scale well, and many could 
in fact reach a timeout without getting to an instance. Again, this is a 
plausible explanation, but not confirmed by any real data. You can read in 
the docs some advice on how the scaling settings work 
, and how to best design 
for scaling events 
. Of course, as 
usual, if you have a specific issue, feel free to provide a report in the 
issue tracker .

On Monday, November 2, 2015 at 9:05:30 PM UTC-5, Kaan Soral wrote:
>
> Yes, AppEngine can't handle bursts well, so the solution is to slow things 
> down
>
> Actually, there are speed limits on a lot of things that are usually not 
> advertised well, if you are getting these kind of errors, try to slow 
> things down and see how it goes
>
> Slowing things down is also pretty challenging, much harder than building 
> stuff that will scale
>
> On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote:
>>
>> Hi,
>>
>> Did you find the reason of these errors?
>>
>> I also see a lot of them. The time which is elapsed is about 10 min, so 
>> it seems that there are tasks that are stuck for some reason in the task 
>> queue.
>>
>> Any insights on that?
>>
>> Thanks
>> Alexandra
>>
>> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>>
>>> "Request was aborted after waiting too long to attempt to service your 
>>> request."
>>>
>>> I've been seeing these messages a lot lately, momentarily many requests 
>>> log these errors, it floods the error logs
>>>
>>> Anyone else?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a3d5858f-6d8b-4656-953a-2df06119c94c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-12 Thread Mario 
In order to help you further, you'd need to provide more information about 
when you see those messages, kind of instances you're using, programming 
language, etc.

On Saturday, April 11, 2015 at 7:02:34 PM UTC+2, Kaan Soral wrote:
>
> "Request was aborted after waiting too long to attempt to service your 
> request."
>
> I've been seeing these messages a lot lately, momentarily many requests 
> log these errors, it floods the error logs
>
> Anyone else?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/35203f66-4a18-4458-9b53-63c9d86c9ee6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-13 Thread Cody Landgrebe 
Kaan,

Looking at the SDK release notes and current version of GAE console app 
engine release 1.9.19 notes have not been published yet; but from research 
my assumption is that the logging level was changed from info to error in 
the latest version. If you look through your logs prior to the move to .19 
I assume that you will have the same messages but logged as info.

On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:
>
> "Request was aborted after waiting too long to attempt to service your 
> request."
>
> I've been seeing these messages a lot lately, momentarily many requests 
> log these errors, it floods the error logs
>
> Anyone else?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c45d987d-83d3-4714-bde9-20f88ea089d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-13 Thread Kaan Soral 
Hi Cody

That makes an extreme amount of sense, it would also explain a lot of the 
inconsistent behaviours of appengine, especially invisibly exhausted 
taskqueue retries

I checked the logs, however, although my log storage is more than enough, 
for some reason the phrase "aborted"/".*aborted.*" didn't produce any 
results, didn't pursue the issue further, the log routines are annoying at 
best

Mario, the instances are:
instance_class: F2
automatic_scaling:
  min_idle_instances: 1
  max_idle_instances: 1
  max_pending_latency: 900ms

The issue has been happening in bursts lately

On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:
>
> Kaan,
>
> Looking at the SDK release notes and current version of GAE console app 
> engine release 1.9.19 notes have not been published yet; but from 
> research my assumption is that the logging level was changed from info to 
> error in the latest version. If you look through your logs prior to the 
> move to .19 I assume that you will have the same messages but logged as 
> info.
>
> On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:
>>
>> "Request was aborted after waiting too long to attempt to service your 
>> request."
>>
>> I've been seeing these messages a lot lately, momentarily many requests 
>> log these errors, it floods the error logs
>>
>> Anyone else?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/53ecd87f-f901-4a33-bcd9-b45513020dc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-14 Thread Mario 
Hi Kaan,

This error is sometimes created by your requests going over the memory 
limit of your instance. You could try to update the instance to F4 or to 
make your requests to process data in smaller chunks. 

Mario

On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:
>
> Hi Cody
>
> That makes an extreme amount of sense, it would also explain a lot of the 
> inconsistent behaviours of appengine, especially invisibly exhausted 
> taskqueue retries
>
> I checked the logs, however, although my log storage is more than enough, 
> for some reason the phrase "aborted"/".*aborted.*" didn't produce any 
> results, didn't pursue the issue further, the log routines are annoying at 
> best
>
> Mario, the instances are:
> instance_class: F2
> automatic_scaling:
>   min_idle_instances: 1
>   max_idle_instances: 1
>   max_pending_latency: 900ms
>
> The issue has been happening in bursts lately
>
> On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:
>>
>> Kaan,
>>
>> Looking at the SDK release notes and current version of GAE console app 
>> engine release 1.9.19 notes have not been published yet; but from 
>> research my assumption is that the logging level was changed from info to 
>> error in the latest version. If you look through your logs prior to the 
>> move to .19 I assume that you will have the same messages but logged as 
>> info.
>>
>> On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:
>>>
>>> "Request was aborted after waiting too long to attempt to service your 
>>> request."
>>>
>>> I've been seeing these messages a lot lately, momentarily many requests 
>>> log these errors, it floods the error logs
>>>
>>> Anyone else?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f3b499bc-a35f-4f01-9e34-8c9589b4958c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-19 Thread Kaan Soral 
I started regularly getting 200-1000 of these in batches

Not sure what to do about them

My other app that handles more requests never has them, I'm guessing they 
are related to instance bursts, the app that experiences the issue probably 
bursts instances too much

I don't think the issue is memory related, as in that case, the instances 
usually die with the critical memory error

On Tuesday, April 14, 2015 at 10:58:20 AM UTC+3, Mario wrote:
>
> Hi Kaan,
>
> This error is sometimes created by your requests going over the memory 
> limit of your instance. You could try to update the instance to F4 or to 
> make your requests to process data in smaller chunks. 
>
> Mario
>
> On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:
>>
>> Hi Cody
>>
>> That makes an extreme amount of sense, it would also explain a lot of the 
>> inconsistent behaviours of appengine, especially invisibly exhausted 
>> taskqueue retries
>>
>> I checked the logs, however, although my log storage is more than enough, 
>> for some reason the phrase "aborted"/".*aborted.*" didn't produce any 
>> results, didn't pursue the issue further, the log routines are annoying at 
>> best
>>
>> Mario, the instances are:
>> instance_class: F2
>> automatic_scaling:
>>   min_idle_instances: 1
>>   max_idle_instances: 1
>>   max_pending_latency: 900ms
>>
>> The issue has been happening in bursts lately
>>
>> On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:
>>>
>>> Kaan,
>>>
>>> Looking at the SDK release notes and current version of GAE console app 
>>> engine release 1.9.19 notes have not been published yet; but from 
>>> research my assumption is that the logging level was changed from info to 
>>> error in the latest version. If you look through your logs prior to the 
>>> move to .19 I assume that you will have the same messages but logged as 
>>> info.
>>>
>>> On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 "Request was aborted after waiting too long to attempt to service your 
 request."

 I've been seeing these messages a lot lately, momentarily many requests 
 log these errors, it floods the error logs

 Anyone else?

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dd95effc-f4a9-46c5-8e06-630b8072093e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-22 Thread Mario 
Hi,

What are those requests that result in errors?

On Sunday, April 19, 2015 at 8:53:24 PM UTC+2, Kaan Soral wrote:
>
> I started regularly getting 200-1000 of these in batches
>
> Not sure what to do about them
>
> My other app that handles more requests never has them, I'm guessing they 
> are related to instance bursts, the app that experiences the issue probably 
> bursts instances too much
>
> I don't think the issue is memory related, as in that case, the instances 
> usually die with the critical memory error
>
> On Tuesday, April 14, 2015 at 10:58:20 AM UTC+3, Mario wrote:
>>
>> Hi Kaan,
>>
>> This error is sometimes created by your requests going over the memory 
>> limit of your instance. You could try to update the instance to F4 or to 
>> make your requests to process data in smaller chunks. 
>>
>> Mario
>>
>> On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:
>>>
>>> Hi Cody
>>>
>>> That makes an extreme amount of sense, it would also explain a lot of 
>>> the inconsistent behaviours of appengine, especially invisibly exhausted 
>>> taskqueue retries
>>>
>>> I checked the logs, however, although my log storage is more than 
>>> enough, for some reason the phrase "aborted"/".*aborted.*" didn't produce 
>>> any results, didn't pursue the issue further, the log routines are annoying 
>>> at best
>>>
>>> Mario, the instances are:
>>> instance_class: F2
>>> automatic_scaling:
>>>   min_idle_instances: 1
>>>   max_idle_instances: 1
>>>   max_pending_latency: 900ms
>>>
>>> The issue has been happening in bursts lately
>>>
>>> On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:

 Kaan,

 Looking at the SDK release notes and current version of GAE console app 
 engine release 1.9.19 notes have not been published yet; but from 
 research my assumption is that the logging level was changed from info to 
 error in the latest version. If you look through your logs prior to the 
 move to .19 I assume that you will have the same messages but logged as 
 info.

 On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:
>
> "Request was aborted after waiting too long to attempt to service 
> your request."
>
> I've been seeing these messages a lot lately, momentarily many 
> requests log these errors, it floods the error logs
>
> Anyone else?
>


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/570dfd18-afe0-4165-8bd6-e8f1f2a86da6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

2015-04-22 Thread Kaan Soral 
They are all *taskqueue* tasks on a *module* with *F2*'s

I think out of the 3, the module aspect might be the cause, as I don't 
experience the issue on other systems

On Wednesday, April 22, 2015 at 11:42:31 AM UTC+3, Mario wrote:
>
> Hi,
>
> What are those requests that result in errors?
>
> On Sunday, April 19, 2015 at 8:53:24 PM UTC+2, Kaan Soral wrote:
>>
>> I started regularly getting 200-1000 of these in batches
>>
>> Not sure what to do about them
>>
>> My other app that handles more requests never has them, I'm guessing they 
>> are related to instance bursts, the app that experiences the issue probably 
>> bursts instances too much
>>
>> I don't think the issue is memory related, as in that case, the instances 
>> usually die with the critical memory error
>>
>> On Tuesday, April 14, 2015 at 10:58:20 AM UTC+3, Mario wrote:
>>>
>>> Hi Kaan,
>>>
>>> This error is sometimes created by your requests going over the memory 
>>> limit of your instance. You could try to update the instance to F4 or to 
>>> make your requests to process data in smaller chunks. 
>>>
>>> Mario
>>>
>>> On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:

 Hi Cody

 That makes an extreme amount of sense, it would also explain a lot of 
 the inconsistent behaviours of appengine, especially invisibly exhausted 
 taskqueue retries

 I checked the logs, however, although my log storage is more than 
 enough, for some reason the phrase "aborted"/".*aborted.*" didn't produce 
 any results, didn't pursue the issue further, the log routines are 
 annoying 
 at best

 Mario, the instances are:
 instance_class: F2
 automatic_scaling:
   min_idle_instances: 1
   max_idle_instances: 1
   max_pending_latency: 900ms

 The issue has been happening in bursts lately

 On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:
>
> Kaan,
>
> Looking at the SDK release notes and current version of GAE console 
> app engine release 1.9.19 notes have not been published yet; but from 
> research my assumption is that the logging level was changed from info to 
> error in the latest version. If you look through your logs prior to the 
> move to .19 I assume that you will have the same messages but logged as 
> info.
>
> On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:
>>
>> "Request was aborted after waiting too long to attempt to service 
>> your request."
>>
>> I've been seeing these messages a lot lately, momentarily many 
>> requests log these errors, it floods the error logs
>>
>> Anyone else?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3eec7dc1-b5f9-4aa2-a4d6-669a25913ff3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.