无法检索状态为:404 - Google App Engine的API配置 [英] Failed to retrieve API configs with status: 404 - Google App Engine

查看:111
本文介绍了无法检索状态为:404 - Google App Engine的API配置的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试在真实设备上调试helloword样本。经过大量的搜索,我设法做了一些设置。



我在实际设备上进行了什么调试:




  • 我已将 LOCAL_APP_ENGINE_SERVER_URL_FOR_ANDROID 的值更改为 http://192.168.1.107:8888 (我的电脑ip地址)

  • 添加 - address = 192.168.1.107 运行配置程序参数,现在看起来像 - address = 192.168.1.107 --port = 8888< path-to-project> / war

  • 引擎应用程序作为Web应用程序,服务器启动sucessfuly,我可以管理服务器应用程序在 http://192.168.1.107:8888/_ah/admin/



不幸的是,当我尝试在真实设备上进行通信时,我得到的是:



GoogleJsonResponseException:500无法检索API配置状态为:404



附有堆栈跟踪的完整错误html内容:

  com.google.api.client.googleapis.json.GoogleJsonResponse异常:500无法检索具有状态的API配置:404 
< html>
< head>
< meta http-equiv =Content-Typecontent =text / html; charset = ISO-8859-1/>
< title>错误500无法检索具有状态的API配置:404< / title>
< / head>
< body>< h2> HTTP ERROR 500< / h2>
< p>问题访问/_ah/api/userendpoint/v1/user/jacek@gmail.com/11224。原因:
< pre>无法检索具有状态的API配置:404< / pre>< / p>< h3>导致:< / h3>< pre> java.io.IOException:无法检索具有状态的API配置:404
com.google.api.server.spi.tools.devserver.ApiServlet.getApiConfigSources(ApiServlet.java:102)
com.google.api.server.spi.tools.devserver.ApiServlet.initConfigsIf必需的(ApiServlet.java:67)
在com.google.api.server.spi.tools.devserver.RestApiServlet.service(RestApiServlet.java:117)
在javax.servlet.http.HttpServlet.service (HttpServlet.java:717)
在org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler .java:1166)
com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter (ServletHandler.java:1157)
com.google.appengine.tools.development .ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
在com.google.appengine.tools.development .HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
com.google.appengine.api.blobstore .dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:63)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
在com.google.apphosting.utils .servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
com.google.appengine.tools .development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java: 1157)
com.google.appengine.tools.development.DevAppServerModulesFilter.doDirectRequest(DevAppServerModulesFilter.java:368)
com.google.appengine.tools.development.DevAppServerModulesFilter.doDirectModuleRequest(DevAppServerModulesFilter.java: 351)
在com.google.appengine.tools.development.DevAppServerModulesFilter.doFilter(DevAppServerModulesFilter.java:116)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java: 1157)
在org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
在org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
在org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
在org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
在org .com (DevAppEngineWebAppContext.java:97)
在org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
com.google.appengine.tools.development.JettyContainerService $ ApiProxyHandler.handle (JettyContainerService.java:485)
在org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
在org.mortbay.jetty.Server.handle(Server.java:326 )
在org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
在org.mortbay.jetty.HttpConnection $ RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
在org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
在org.mortbay.jetty.HttpConnection。 handle(HttpConnection.java:404)
在org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
在org.mortbay.thread.QueuedThreadPool $ PoolThread.run(QueuedThreadPool。 java:582)
< / pre> ;
< hr />< i>< small> Powered by Jetty://< / small>< / i>< br />
< / body>
< / html>

所以看起来我已经与后端通信了,但是有一些原因现在不行。

解决方案

实际上只需设置 - address = 0.0.0.0 --port = 8888 在启动配置参数中修复了问题。



其余的设置保持在问题中。


I'm trying to debug the helloword sample on real device. After lots of searching, I've managed to do some settings.

What I did to debug on real device:

  • I've changed LOCAL_APP_ENGINE_SERVER_URL_FOR_ANDROID value to http://192.168.1.107:8888 (my computer ip address)
  • Added --address=192.168.1.107 to run configuration program params so now it looks like --address=192.168.1.107 --port=8888 "<path-to-project>/war"
  • Ran app engine app as web application, server started sucessfuly and I can administrate server app on http://192.168.1.107:8888/_ah/admin/

Unfortunately when I try communicate on real device all i get is:

GoogleJsonResponseException: 500 Failed to retrieve API configs with status: 404

There is full error html content with stack trace attached:

com.google.api.client.googleapis.json.GoogleJsonResponseException: 500 Failed to retrieve API configs with status: 404
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 500 Failed to retrieve API configs with status: 404</title>
</head>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /_ah/api/userendpoint/v1/user/jacek@gmail.com/11224. Reason:
<pre>    Failed to retrieve API configs with status: 404</pre></p><h3>Caused by:</h3><pre>java.io.IOException: Failed to retrieve API configs with status: 404
    at com.google.api.server.spi.tools.devserver.ApiServlet.getApiConfigSources(ApiServlet.java:102)
    at com.google.api.server.spi.tools.devserver.ApiServlet.initConfigsIfNecessary(ApiServlet.java:67)
    at com.google.api.server.spi.tools.devserver.RestApiServlet.service(RestApiServlet.java:117)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
    at com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:63)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at com.google.appengine.tools.development.DevAppServerModulesFilter.doDirectRequest(DevAppServerModulesFilter.java:368)
    at com.google.appengine.tools.development.DevAppServerModulesFilter.doDirectModuleRequest(DevAppServerModulesFilter.java:351)
    at com.google.appengine.tools.development.DevAppServerModulesFilter.doFilter(DevAppServerModulesFilter.java:116)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
    at com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:97)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:485)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
</pre>
<hr /><i><small>Powered by Jetty://</small></i><br/>   
</body>
</html>

SO it looks like I've communicated with backend, but foor some reason it won't work now. There is no such error when working on localhost and emulator.

解决方案

Actually just setting --address=0.0.0.0 --port=8888 in launch configuration params fixed the issue.

Rest of the settings stayed as in the question.

这篇关于无法检索状态为:404 - Google App Engine的API配置的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆