本文介绍了调用Import-AzureRmApiManagementApi时的网关超时的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们订阅的所有APIM都在下面抛出错误。细节是$


我们有一个从后端下载swagger文件的脚本。然后通过Import命令向上推送该文件。

这是APIM中现有API的更新,并且确实有很多变化。

这是一个非常大的招摇file(700k ish)

作为一种尝试解决问题的方法,我们删除了API并执行导入。它第一次工作正常。之后,如果我们再次推送SAME文件。我们得到了同样的问题。

我们将实例升级到标准,看看是否可以缓解这个问题。它没有。



任何想法都会受到赞赏! 



" subStatus":{



" value": 

" GatewayTimeout",


" localizedValue": 

"网关超时(HTTP状态代码:504)"



},



" submissionTimestamp": 

" 2018-08-11T11:45:45.0859067Z",



" properties" ;: {



" statusCode": 

" GatewayTimeout" ,



" serviceRequestId": 

null,



" statusMessage": 

" {\" error \":{\" code\":\" GatewayTimeout \", \\"message \":\&";网关在指定的时间段内未收到来自"Microsoft.ApiManagement"的回复。\"} }" b
$
},

All of the APIM's in one of our subscriptions are throwing the error below. The specifics are

We have a script to download the swagger file from the backend. That file is then pushed upvia the Import command.
This is an UPDATE of an existing API in APIM and does have quite a few changes.
This is a pretty large swagger file (700k ish)
As a means to try and figure it out we deleted the API and performs the import. It works fine first time. After that if we push the SAME file again. We get the same issue.
We upsized the instance to standard to see if that would mitigate the issue. It did not.

Any thoughts would be appreciated! 

"subStatus": {

"value": 
"GatewayTimeout",

"localizedValue": 
"Gateway Timeout (HTTP Status Code: 504)"

},

"submissionTimestamp": 
"2018-08-11T11:45:45.0859067Z",

"properties": {

"statusCode": 
"GatewayTimeout",

"serviceRequestId": 
null,

"statusMessage": 
"{\"error\":{\"code\":\"GatewayTimeout\",\"message\":\"The gateway did not receive a response from 'Microsoft.ApiManagement' within the specified time period.\"}}"

},




推荐答案

------------------------------------------- -------------------------------------------------- -


这篇关于调用Import-AzureRmApiManagementApi时的网关超时的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

11-01 19:07