[
https://issues.apache.org/jira/browse/MRESOLVER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807819#comment-17807819
]
ASF GitHub Bot commented on MRESOLVER-464:
------------------------------------------
rmannibucau commented on PR #408:
URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1896260133
why not using `jdk.httpclient.maxstreams`? I kind of fail to see how a
semaphore helps, we should just ensure to respect server settings no, so a
"warmup" call then we know and just use the right number of connections so
sounds like we misuse http2 and delegate the fact it works to end user, hope im
missing something
> 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
> 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)
