[
https://issues.apache.org/jira/browse/MRESOLVER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807840#comment-17807840
]
ASF GitHub Bot commented on MRESOLVER-464:
------------------------------------------
rmannibucau commented on PR #408:
URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1896342446
It works cause it is per connection but agree it is bad from a design
standpoint - but it is http2, we cant help.
As a side note my thread count for resolver is always 512 (just to enable as
much concurrent downloads but having 4 threads is sufficient for an async impl
- just to highlight it is what we should target in terms of concurrent
downloads, not threads).
About async helping it is just cause you chain more easily without adding a
queue but agree it is an impl detail.
Now about your fix we still have the same issue, you set it to 100 but then
it is set to 12 so maybe we should revert and default to http1?
> 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)
