cstamas commented on PR #408: URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1896309679
Wrong, as if remote server on first response tells client "my max_concurrent_stream=12" then client will have to obey it AFAIK. Again, see first paragraph. Yes, instead of Integer.MAX_VALUE it will be set to 100, but on first response to 12. So what gives? Creating more clients does not help (as I read). Same thing happens. Async flavor does not helps (as I read), same thing happens. Finally, this "works" as without this change the JBang UT fails with "java.io.IOException: too many concurrent streams", while with this change the error is gone and UT passes OK. Again, this was never hit in Maven (nor can, as Resolver operates with pools of size 4-8, not 100s). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
