You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The services which support Http2 streaming might limit max concurrent connections on the server side. This leads to an error being thrown if concurrent requests more than maxConcurrentConnections are created on the client side which share an HTTP2 session.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Is your feature request related to a problem? Please describe.
The services which support Http2 streaming might limit max concurrent connections on the server side. This leads to an error being thrown if concurrent requests more than
maxConcurrentConnections
are created on the client side which share an HTTP2 session.The issue with AWS Transcribe Streaming is explained in repo https://github.com/jjtindale/aws-parallel-transcribe-repro
The error thrown in Node.js with concurrent requests more than
maxConcurrentConnections
is explained in https://github.com/trivikr/node-http2-parallel-requests-on-sessionDescribe the solution you'd like
Add an option to disable session cache in NodeHttp2Handler. This would ensure that a new session is created for every request.
For example:
Describe alternatives you've considered
Write my own Http2Handler which does not share ClientHttp2Sessions between requests.
The text was updated successfully, but these errors were encountered: