[
https://issues.apache.org/jira/browse/FLINK-18155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126701#comment-17126701
]
Robert Metzger commented on FLINK-18155:
----------------------------------------
There is already a PR for disabling the JMX integration:
https://github.com/apache/flink/pull/12433/files
One disadvantage of disabling it is that we are not running Flink in the same
way the users would run it in production.
We also need to understand if the JMX server is really the cause for slow test
startup (if that's true)
> Disable Log4j's JMX for (integration)tests
> -------------------------------------------
>
> Key: FLINK-18155
> URL: https://issues.apache.org/jira/browse/FLINK-18155
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Robert Metzger
> Priority: Minor
>
> There were reports about Log4j2 initializing slowly when executing tests
> locally.
> The root cause of this has not been understood yet, but we know that Log4j is
> starting a JXM server, which could be responsible for the slow startup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
