[
https://issues.apache.org/jira/browse/MRESOLVER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807845#comment-17807845
]
ASF GitHub Bot commented on MRESOLVER-464:
------------------------------------------
cstamas commented on PR #408:
URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1896389068
> 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?
Hence the "workaround": exposed config settable _globally_ but also _per
repository_. 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".
As checked with curl site, the value is usually 100 or 128 or above. I
expect exotic values in "closed environments" like companies etc, but there
again, Maven dev can consult IT about these values (or try, fail, adapt,
loop)...
> 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)
