[
https://issues.apache.org/jira/browse/MRESOLVER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808647#comment-17808647
]
ASF GitHub Bot commented on MRESOLVER-464:
------------------------------------------
cstamas commented on PR #408:
URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1900395350
Usually remote reposes have different URLs (usually different hosts), so
yes, a repo is one distinct connection. Usually. I may imagine someone defines
central1, central2, etc and all point to central, but I find it highly not
plausible.
This workaround is about "concurrent requests", that in HTTP/2 is
"concurrent streams" while in HTTP/1.1 is usually "concurrent requests". Also,
unsure why you keep repeating "not work": check out the reproducer, w/o this
commit it will reproduce the error (IOEx: too many concurrent streams) and with
this commit it will work OK. So it works. From where you get that "the fix does
not help?".
The http2 _is reliable by default_, did you try it out? Of course, currently
it is only Maven Central that supports it fully, as all the MRMs out there are
HTTP/1.1 only.
> 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)
