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:45:00 UTC

[jira] [Updated] (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 updated KAFKA-14430:
----------------------------------
    Description: 
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]

 

  was:
In case the server has a firewall, exposing only 'com.sun.management.jmxremote.port' cannot fetch metrics, and when the rmi port is not specified, it is randomly generated by default, 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]

_Summary of testing strategy (including rationale)_
_for the feature or bug fix. Unit and/or integration_
_tests are expected for any behaviour change and_
_system tests should be considered for larger changes._

 


> 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
>            Priority: Minor
>
> 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)