[
https://issues.apache.org/jira/browse/FLINK-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290751#comment-17290751
]
Matthias commented on FLINK-21499:
----------------------------------
Hi [~Tony Giao], thanks for reporting this issue. Could you provide the exact
{{mvn}} command you executed? You're mentioning {{-t}} option in the
description but talk about multi-threading in the headline which makes me think
that your actually talking about {{-T}} here. Looking into MSHADE-384 (which
seems to be related) supports this assumption. Could you verify (and fix) the
issue accordingly?
Another question: is this behavior only happening when running {{package}} on
the overall project or could we pin this down to sub-modules as well using
{{-DskipTests}} or even {{compile}} (as you mentioned that the behavior happens
during compilation)? I'm asking because I wasn't able to reproduce it using the
{{flink-walkthrough}} module mentioned in your screenshot.
> maven package hang when using multithread on jdk 11
> ---------------------------------------------------
>
> Key: FLINK-21499
> URL: https://issues.apache.org/jira/browse/FLINK-21499
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 1.12.1
> Reporter: Zhengqi Zhang
> Priority: Major
> Attachments: 82210_jstack.txt, image-2021-02-25-14-27-46-087.png
>
>
> When I add the -t parameter to the MVN clean package command, the compilation
> gets stuck. By turning on the Maven Debug log, you can observe a large number
> of repeated logs like the one below, seemingly stuck in an endless loop.
>
> I printed the thread stack and attached it.
>
> !image-2021-02-25-14-27-46-087.png|width=1438,height=876!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
