Geek Answers Handbook

Google Cloud Endpoints on Managed Virtual Machines

We had a working solution for Cloud Endpoints on the standard AppEngine, but recently we switched to managed virtual machines https://cloud.google.com/appengine/docs/java/managed-vms/

Everything seems to work the same, except for Cloud Endpoints.

I have the same results for the production of managed virtual machines and the local docker dev environment.

Some suspicious lines from the gcloud preview app runoutput:

INFO: default: "POST /_ah/spi/BackendService.getApiConfigs HTTP/1.1" 404 29
INFO: default: "GET /_ah/api/discovery/v1/apis/admin/v1/rest?fields=servicePath%2Cresources%2Cparameters%2Cmethods&pp=0 HTTP/1.1" 500 60

I can’t find out if Google Cloud Endpoints are supported on managed virtual machines in general? And if they are supported, what should I do to fix this problem?

+4
source share
3 answers

The problem was resolved on its own. I switched to jax-rs until the endpoints of the cloud worked. I recently tried switching back the endpoints of the clouds, which worked fine. Perhaps this is due to the appengine version, I'm sure. There were several version updates when I was on jax-rs.

0
source

getApiConfigs returning 404 is a sign that something is wrong with the request for /_ah/spi/*- no handler was found. You should have defined a handler in your web.xml for this route when setting up your endpoint project. For this reason, the GET path to the discovery path is detected with 500 because it internally calls the first path.

0
source

Cloud endpoints are not supported on managed virtual machines. You must get away from this combination if you want to avoid problems in the future.

0
source

More articles:


All Articles