[
https://issues.apache.org/jira/browse/MRESOLVER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808683#comment-17808683
]
ASF GitHub Bot commented on MRESOLVER-464:
------------------------------------------
rmannibucau commented on PR #408:
URL: https://github.com/apache/maven-resolver/pull/408#issuecomment-1900525709
@cstamas can you point out the reproducer? The thing is that http2 without
ssl uses a pool whereas it does not over ssl and there the system property is a
similar workaround than a semaphore but with a more relevant limitation than
the semaphore which is global whatever the number of connection is - you dont
know from consumer side, so yes semaphore is still as buggy as before even if
issues pops up less often (didnt check on 11 and 21 but it is the bahvior on
jre17, dont know if it changed)
> 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)
