GAE / Google API刷新访问令牌的DeadlineExceededErrors [英] DeadlineExceededErrors with GAE/Google API refreshing access token

查看:89
本文介绍了GAE / Google API刷新访问令牌的DeadlineExceededErrors的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在过去几天里,我的GAE应用程序中遇到了与Google Calendar API交互的DeadlineExceededErrors。据我所知,这些错误是零星的;我昨天晚上没有得到这些错误,但昨天在白天和今天早上。当我在本地开发环境中运行时,我没有获取这些错误,这让我想知道GAE服务器正在发生什么情况以导致此问题以及我如何解决此问题。

我尝试将我的urlFetch截止日期设置为45-60,但它没有任何区别。我也尝试建立一个超时时间很长的HTTP对象,但没关系。日志看起来像这样:

  2013-06-07 11:21:06.079 make:Got type< class'google。 appengine.api.datastore_types.Blob'> 
I 2013-06-07 11:21:06.081 validate:Got type< class'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.086 make:Got type< class'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.087 validate:Got type< class'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.093 make:Got type< class'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.093 validate:Got type< class'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.094请求的网址:https://www.googleapis.com/discovery/v1/apis/calendar/v3/rest?userIp = 99.19.70.243
I 2013-06-07 11:21:06.153请求的URL:https://www.googleapis.com/calendar/v3/calendars/primary/events?alt=json
I 2013-06-07 11: 21:06.201因为401
I刷新2013-06-07 11:21:06.207 make:Got type< class'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.208 validate:Got type< class'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.208刷新access_token
E 2013-06-07 11:21:15.989在等待来自URL的HTTP响应时超出了截止日期:https://accounts.google。 com / o / oauth2 / token Traceback(最近调用最后一次):File/ py

它现在窒息了刷新过程?



编辑:我应该补充说我的应用与Facebook API交互,并且我没有收到DEE。

解决方案

我认为这可能是由于这个问题?


2013年6月7日,美国/太平洋地区下午5:15
解决了Google App Engine URL提取服务对Google
帐户身份验证终端的问题。我们对给您带来的不便表示歉意,
感谢您的耐心和持续的支持。请放心,
系统可靠性是Google的首要任务,我们正在不断改进
,以使我们的系统更好。


https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/TqKVL9TNq2A


Over the last few days I have been encountering DeadlineExceededErrors in my GAE app that interacts with the Google Calendar API. As far as I know these errors have been sporadic; I was not given these errors last night, but was during yesterday during the day and now this morning. I am not getting these errors when I run on the local dev environment, which makes me wonder what is going on with the GAE servers to cause this issue and how I can fix it.

I tried setting my urlFetch deadline to 45-60 but it didn't make a difference. I also tried building an HTTP object with a high timeout, but it didn't matter. The log looks like this:

2013-06-07 11:21:06.079 make: Got type <class 'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.081 validate: Got type <class 'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.086 make: Got type <class 'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.087 validate: Got type <class 'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.093 make: Got type <class 'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.093 validate: Got type <class 'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.094 URL being requested: https://www.googleapis.com/discovery/v1/apis/calendar/v3/rest?userIp=99.19.70.243
I 2013-06-07 11:21:06.153 URL being requested: https://www.googleapis.com/calendar/v3/calendars/primary/events?alt=json
I 2013-06-07 11:21:06.201 Refreshing due to a 401
I 2013-06-07 11:21:06.207 make: Got type <class 'google.appengine.api.datastore_types.Blob'>
I 2013-06-07 11:21:06.208 validate: Got type <class 'oauth2client.client.OAuth2Credentials'>
I 2013-06-07 11:21:06.208 Refreshing access_token
E 2013-06-07 11:21:15.989 Deadline exceeded while waiting for HTTP response from URL: https://accounts.google.com/o/oauth2/token Traceback (most recent call last): File "/py

Why is it choking on the refresh process now?

Edit: I should add that my app interacts with the Facebook API as well and I am not receiving DEEs for that.

解决方案

I think it may have been due to this issue?

The problem with Google App Engine URL Fetch service to Google Accounts authentication endpoints was resolved as of 5:15 PM US/Pacific on June 7, 2013. We apologize for the inconvenience and thank you for your patience and continued support. Please rest assured that system reliability is a top priority at Google, and we are making continuous improvements to make our systems better.

https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/TqKVL9TNq2A

这篇关于GAE / Google API刷新访问令牌的DeadlineExceededErrors的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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