Java 7 Standard environment - Error code 204

68 views
Skip to first unread message

D. Kash

unread,
Oct 12, 2017, 1:02:59 PM10/12/17
to Google App Engine
Hello, 

We are using Java 7 Standard environment.

With B8 instances and basic scaling. 
    <instance-class>B8</instance-class>
    <basic-scaling>
        <max-instances>8</max-instances>
        <idle-timeout>15m</idle-timeout>
    </basic-scaling>

These instances used only to handle deferred tasks execution.  And after some period of running (from 4 to 12 hours), we are getting :

A problem was encountered with the process that handled this request, causing it to exit. This is likely to cause a new process to be used for the next request to your application. (Error code 204)

With the 500 response code. to _ah/queue/__deferred__ request.   

We think that this is happening because of RAM issue. But as far as I know, there are no ways to profile memory on the App Engine Standard environment.  

Locally we can't reproduce some memory leaks. 

So my questions are following: 
1) Is this issue caused by out of memory or something else? 
2) Is there any way to profile memory usage with App Engine?

Regards

Kenworth (Google Cloud Platform)

unread,
Oct 12, 2017, 4:28:51 PM10/12/17
to google-a...@googlegroups.com
There is currently no native memory profiler for App Engine Standard, but it does sound like a good feature request to make on the issue tracker. You probably won't be able to completely avoid request timeouts due to memory pressure with Basic scaling. With Manual scaling you can avoid them using a 'fail fast' strategy and controlling your instance lifecycle, and with Automatic scaling you can avoid them by controlling concurrency.  

Based on the information you provided, it's too early to tell whether it is related to a memory issue. The issue will most likely lead to a specific situation and I suspect may require some exchange of code/project information to reproduce the behavior you described. In this case, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it. We monitor that issue tracker closely.

I look forward to this issue report.
Reply all
Reply to author
Forward
0 new messages