500 error on first boot

[William Shakour]

I am using java8 std env on appengine and getting a 500 error when hitting a url for the first time:

Error: Server Error

The server encountered an error and could not complete your request.

Please try again in 30 seconds.

as soon as I refresh the application comes to life with expected first time load delay.

These 2 messages are from the app engine logs

The process handling this request unexpectedly died. This is likely to cause a new process to be used for the next request to your application. (Error code 203)

followed by

This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application

as expected.

Any ideas why that might be happening?

Thanks.

[Kamran (Google Cloud Support)]

Are you deploying a code from Google Cloud Tutorials or this is your own code? I'd recommend visiting this thread where a similar issue has been discussed.

[William Shakour]

Hi Kamran, 

Thanks for the reply.

I am using my own code (it is an open source project https://github.com/billy1380/blogwt). I checked the thread above and it does not look like the same thing (also using java8 beta not go). I only get the error once if the site has been dormant and if I press refresh the site comes up.

The code is deployed to multiple app engine projects  and can be reached on these different instances http://blogwtproject.appengine.com, https://www.mwperfumes.com and https://www.willshex.com

They all seem to have the same issue... 500 first (once) then no issues after that.

William

[Jordan (Cloud Platform Support)]

This is currently a known issue and our engineering team is investigating the cause. Note that Java 8 is currently in beta, and that there is no ETA for the fix at this time. 

The issue is due to an RPC failure possibly due to your instance's Java 8 runtime not being completely ready on your first request. If the instance was started via a warmup request you may be able to load your actual application code with the instance via the load-on-startup option in order to completely ready the instance to accept requests.  

- All further communications about this issue should occur in the public issue tracker. 

[William Shakour]

Thanks for letting me know... I was not aware of the bug or the public issue tracker for that matter. So much appreciated on both counts.