[
https://issues.apache.org/jira/browse/MRESOLVER-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-455:
--------------------------------------
Description:
The JDK transport may cause JVM to become "stuck" and become unable to cleanly
exit.
Based on [https://bugs.openjdk.org/browse/JDK-8308364] the problem is:
In case of errors the response stream is not even touched (despite
ofInputStream handler is used), and hence if response contains some content
(ie. error page) the client will get stuck.
This is currently observed on Java 21, while 17 and 11 and 8 (as on Java 8 JDK
transport is not used) are ok.
was:
The JDK transport may cause JVM to become "stuck" and become unable to cleanly
exit.
Based on [https://bugs.openjdk.org/browse/JDK-8308364] the problem is:
In case of errors the response stream is not even touched (despite
ofInputStream handler is used), and hence if response contains some content
(ie. error page) the client will get stuck.
> JDK transport: Improper handling of ofInputStream body handlers in case of
> error
> --------------------------------------------------------------------------------
>
> Key: MRESOLVER-455
> URL: https://issues.apache.org/jira/browse/MRESOLVER-455
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Affects Versions: 2.0.0-alpha-3, 2.0.0-alpha-4
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0-alpha-5
>
>
> The JDK transport may cause JVM to become "stuck" and become unable to
> cleanly exit.
> Based on [https://bugs.openjdk.org/browse/JDK-8308364] the problem is:
> In case of errors the response stream is not even touched (despite
> ofInputStream handler is used), and hence if response contains some content
> (ie. error page) the client will get stuck.
> This is currently observed on Java 21, while 17 and 11 and 8 (as on Java 8
> JDK transport is not used) are ok.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
