You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Chris Egerton (Jira)" <ji...@apache.org> on 2022/12/02 03:49:00 UTC

[jira] [Assigned] (KAFKA-14430) optimize: -Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT

     [ https://issues.apache.org/jira/browse/KAFKA-14430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Egerton reassigned KAFKA-14430:
-------------------------------------

    Assignee: jianbin.chen

> optimize: -Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT
> -----------------------------------------------------------
>
>                 Key: KAFKA-14430
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14430
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: jianbin.chen
>            Assignee: jianbin.chen
>            Priority: Minor
>             Fix For: 3.4.0, 3.3.2
>
>
> In case the server has a firewall or is run inside a container, exposing only 'com.sun.management.jmxremote.port' cannot fetch metrics, and when the RMI port is not specified, it is randomly generated by default. We should make the two ports consistent for metrics data reading.
> [https://bugs.openjdk.org/browse/JDK-8035404?page=com.atlassian.jira.plugin.system.issuetabpanels%3Achangehistory-tabpanel]
> [https://www.baeldung.com/jmx-ports]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)