我们有一个角度2应用程序随机停止请求15秒。问题似乎是铬/ IP连接耗尽了铬。问题只出在chrome中。请求dosent在chrome dev选项卡中获取连接ID: Shows stalling and no connection id
15秒后响应加载为空。
在chrome:// net-internals /#events中,请求如下:
寻找15秒的差距,铬告诉我什么?
t=543333 [st= 50] HTTP_STREAM_PARSER_READ_HEADERS [dt=15062]
t=558395 [st=15112] HTTP_TRANSACTION_READ_RESPONSE_HEADERS
所有
t=543283 [st= 0] +REQUEST_ALIVE [dt=15113]
--> priority = "MEDIUM"
--> url = "https://www.struqtur.se/hyperion/GraphQl?hyperionRevertParapaar=6.4186284125575295"
t=543283 [st= 0] +URL_REQUEST_DELEGATE [dt=1]
t=543283 [st= 0] DELEGATE_INFO [dt=1]
--> delegate_blocked_by = "tillägget Adblock Plus"
t=543284 [st= 1] -URL_REQUEST_DELEGATE
t=543284 [st= 1] +URL_REQUEST_START_JOB [dt=15111]
--> load_flags = 258 (BYPASS_CACHE | VERIFY_EV_CERT)
--> method = "POST"
--> upload_id = "0"
--> url = "https://www.struqtur.se/hyperion/GraphQl?hyperionRevertParapaar=6.4186284125575295"
t=543284 [st= 1] URL_REQUEST_DELEGATE [dt=0]
t=543284 [st= 1] HTTP_CACHE_GET_BACKEND [dt=0]
t=543284 [st= 1] +HTTP_STREAM_REQUEST [dt=49]
t=543284 [st= 1] HTTP_STREAM_JOB_CONTROLLER_BOUND
--> source_dependency = 45248 (HTTP_STREAM_JOB_CONTROLLER)
t=543333 [st= 50] HTTP_STREAM_REQUEST_BOUND_TO_JOB
--> source_dependency = 45249 (HTTP_STREAM_JOB)
t=543333 [st= 50] -HTTP_STREAM_REQUEST
t=543333 [st= 50] +UPLOAD_DATA_STREAM_INIT [dt=0]
t=543333 [st= 50] UPLOAD_DATA_STREAM_INIT [dt=0]
--> is_chunked = false
--> net_error = 0 (?)
--> total_size = 151
t=543333 [st= 50] -UPLOAD_DATA_STREAM_INIT
--> is_chunked = false
--> net_error = 0 (?)
--> total_size = 151
t=543333 [st= 50] +HTTP_TRANSACTION_SEND_REQUEST [dt=0]
t=543333 [st= 50] HTTP_TRANSACTION_SEND_REQUEST_HEADERS
--> POST /hyperion/GraphQl?hyperionRevertParapaar=6.4186284125575295 HTTP/1.1
Host: www.struqtur.se
Connection: keep-alive
Content-Length: 151
Pragma: no-cache
Cache-Control: no-cache
Accept: application/json, text/plain, */*
Origin: https://www.struqtur.se
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Content-Type: application/json
Referer: https://www.struqtur.se/v2/day/handle
Accept-Encoding: gzip, deflate, br
Accept-Language: sv-SE,sv;q=0.9,en-US;q=0.8,en;q=0.7
Cookie: [408 bytes were stripped]
t=543333 [st= 50] HTTP_TRANSACTION_SEND_REQUEST_BODY
--> did_merge = false
--> is_chunked = false
--> length = 151
t=543333 [st= 50] +UPLOAD_DATA_STREAM_READ [dt=0]
--> current_position = 0
t=543333 [st= 50] UPLOAD_DATA_STREAM_READ [dt=0]
--> current_position = 0
t=543333 [st= 50] -UPLOAD_DATA_STREAM_READ
t=543333 [st= 50] UPLOAD_DATA_STREAM_READ [dt=0]
--> current_position = 151
t=543333 [st= 50] -HTTP_TRANSACTION_SEND_REQUEST
t=543333 [st= 50] +HTTP_TRANSACTION_READ_HEADERS [dt=15062]
t=543333 [st= 50] HTTP_STREAM_PARSER_READ_HEADERS [dt=15062]
t=558395 [st=15112] HTTP_TRANSACTION_READ_RESPONSE_HEADERS
--> HTTP/1.1 200 OK
Date: Mon, 11 Dec 2017 09:01:54 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-cache, no-transform
Pragma: no-cache
Content-Length: 53
Connection: close
Content-Type: application/json
t=558395 [st=15112] -HTTP_TRANSACTION_READ_HEADERS
t=558395 [st=15112] URL_REQUEST_DELEGATE [dt=0]
t=558395 [st=15112] -URL_REQUEST_START_JOB
t=558395 [st=15112] URL_REQUEST_DELEGATE [dt=0]
t=558395 [st=15112] HTTP_TRANSACTION_READ_BODY [dt=0]
t=558395 [st=15112] URL_REQUEST_JOB_FILTERED_BYTES_READ
--> byte_count = 53
t=558395 [st=15112] HTTP_TRANSACTION_READ_BODY [dt=1]
t=558396 [st=15113] -REQUEST_ALIVE
Fininshed request in chrome dev tab
我已经阅读了许多帖子并试图毫无运气地解决问题
Chrome stalls when making multiple requests to same resource?
https://bugs.chromium.org/p/chromium/issues/detail?id=46104
https://bugs.chromium.org/p/chromium/issues/detail?id=447463
我发现的线程/问题类似,但解决方案不起作用,我希望有人有这类问题的经验并且有任何想法
答案 0 :(得分:0)
我在使用Chrome时遇到了同样的问题,但我的应用并没有使用Angular。但是停顿请求的net-internals/#events
条目是相同的,当它们发生时,通常受影响的请求同样会停顿15秒,但通常更像是5-10秒。
在我的情况下,它发生在应用程序访问内部API时,服务器端日志对于停滞的请求完全正常(即API调用不会比平时花费更长时间),所以我知道&# 39; Chrome中的东西客户端应用程序部署在Chromebox上,这可能很重要,因为我无法在我的工作站上重现该问题。
@ torpare-nilsson您是否设法找到更多相关信息?我看到你在Angular的GitHub上打开了一个问题,但又被反弹回SO,这可能是有道理的,因为这看起来像是一个Chrome问题。