[
https://issues.apache.org/jira/browse/MRESOLVER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807860#comment-17807860
]
ASF GitHub Bot commented on MRESOLVER-464:
------------------------------------------
rmannibucau commented on PR #408:
URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1896498271
> So the workaround is that if you hit this issue with remote repository
"foo", then you can check in .mvn/maven.config that sets proper value for
repository "foo" (check the config page diff for new option this PR introduces).
But the limit is per connection so a limit per repo is pointless :thinking:
> As checked with curl site, the value is usually 100 or 128 or above.
Spec mentions 100 but it is the concurrent streams per connection, not the
concurrent connections, see why the fix does not help?
> OR as you propose, fall back to HTTP/1.1
iF we can't make http2 reliable *by default* - without too much reflection
technically speaking - let's ensure the default always works, guess it is the
minimum we should provide.
As mentionned, perf diff is not key enough for maven to be noticeable so no
point defaulting to http2.
> JDK transport bug
> -----------------
>
> Key: MRESOLVER-464
> URL: https://issues.apache.org/jira/browse/MRESOLVER-464
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-7
>
>
> JDK transport seems can be plagued by
> https://bugs.openjdk.org/browse/JDK-8225647
> Try to do something about this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
