-
Notifications
You must be signed in to change notification settings - Fork 114
http2 error #121
Comments
I managed to do a reconnect by modifying worker.go
However, this still does not solve the issue on why I'm getting readFrame error. |
We also reproduce it on Go 1.13. |
The step to reproduce the issue is the following:
Then we can see "http2: no cached connection was available". |
We can see the issue only on Go 1.13. I think that occurs on a compatible problem with Both For Go 1.12, Since Go 1.13, both Go 1.13 stores the connection into the pool after created. I'm not very familiar with Go's internal and http2 implementation, but is it a bug on Go 1.13? |
I tried to reproduce with latest |
I released version 0.12.0. This release includes #130. This should not happen. |
Hi,
I am receiving error for http2 transport. I know it probably is golang issue but how can I force a reconnect when this occurs?
Here is my logs:
2019/09/15 18:19:56 http2: Transport closing idle conn 0xc00034c000 (forSingleUse=false, maxStream=1)
2019/09/15 18:19:56 http2: Transport readFrame error on conn 0xc00034c000: (*net.OpError) read tcp 172.31.21.125:40224->17.188.138.73:443: use of closed network connection
2019/09/15 18:24:02 http2: Transport failed to get client conn for api.development.push.apple.com:443: http2: no cached connection was available
2019/09/15 18:24:02 http2: Transport failed to get client conn for api.development.push.apple.com:443: http2: no cached connection was available
My golang version is 1.13 and I'm using latest version of gaurun.
The text was updated successfully, but these errors were encountered: