[
https://issues.apache.org/jira/browse/IGNITE-25694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-25694:
-----------------------------------------
Description:
In Apache Ignite 2, when JMX is configured, it provides a line in the log
outputting the current configuration.
{noformat}
[INFO][main][IgniteKernal] Remote Management [restart: on, REST: on, JMX
(remote: on, port: 49115, auth: on, ssl: off)]{noformat}
Apache Ignite 3 does not have an equivalent and it doesn’t get stored in the
config so there isn’t a quick way to check the settings without checking
vars.env.
{*}Recommendation{*}:
Output JMX configuration to logs upon node start, like we do in Ignite 2.
was:
In Apache Ignite 2, when JMX is configured, it provides a line in the log
outputting the current configuration.
{noformat}
[INFO][main][IgniteKernal] Remote Management [restart: on, REST: on, JMX
(remote: on, port: 49115, auth: on, ssl: off)]{noformat}
Apache Ignite 3 does not have an equivalent and it doesn’t get stored in the
config so there isn’t a quick way to check the settings without checking
vars.env.
{*}Recommendation{*}:
Output JMX configuration to logs upon node start, like we do in Ignite 2.
> Output JMX configuration to logs
> --------------------------------
>
> Key: IGNITE-25694
> URL: https://issues.apache.org/jira/browse/IGNITE-25694
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> In Apache Ignite 2, when JMX is configured, it provides a line in the log
> outputting the current configuration.
>
> {noformat}
> [INFO][main][IgniteKernal] Remote Management [restart: on, REST: on, JMX
> (remote: on, port: 49115, auth: on, ssl: off)]{noformat}
> Apache Ignite 3 does not have an equivalent and it doesn’t get stored in the
> config so there isn’t a quick way to check the settings without checking
> vars.env.
> {*}Recommendation{*}:
> Output JMX configuration to logs upon node start, like we do in Ignite 2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)