-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b97
The ManagementAgent.status diagnostic command only outputs the specifically set properties, and not any default values, even though the default values are also in effect.
This causes JMC (or the user) to have duplicated information about the default values, such ssl enabledment, JDP settings etc.
For example:
>jcmd 7948 ManagementAgent.start jmxremote.port=7092 jmxremote.authenticate=false
7948:
Command executed successfully
>jcmd 7948 ManagementAgent.status
7948:
Agent: enabled
Connection Type: remote
Protocol : rmi
Host : klara01
URL : service:jmx:rmi://klara01/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHVi
AAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxh
Mx4DAAB4cHciAAtVbmljYXN0UmVmMgEADjEwLjE2MS4xOTAuMTY3AADSonNyACdqYXZheC5ybWkuc3NsLlNzbFJNSUNsaWVudFNvY2tldEZhY3RvcnmMqrS7
gYUlDwIAAHhwdxeVBUcQ0oDc8Ok5v/0AAAFQ8Wb1poABAHg=
Properties :
com.sun.management.jmxremote.authenticate = false
com.sun.management.jmxremote.port = 7092
( Notice that eg. jmxremote.ssl defaults to true, and jmxremote.rmi.port defaults to 7092)
---------------------------
One could imagine another part of the output containing default values in use, something like
Properties :
com.sun.......
Defaults :
com.sun......
I have no idea if this is considered a bug or a feature, or how hard it would be to implement, and I realize that we might have thought about this for the original enhancement/CCC, where we never really specified the output in that detail.
Not sure if the issue should be a bug or an enh.
This causes JMC (or the user) to have duplicated information about the default values, such ssl enabledment, JDP settings etc.
For example:
>jcmd 7948 ManagementAgent.start jmxremote.port=7092 jmxremote.authenticate=false
7948:
Command executed successfully
>jcmd 7948 ManagementAgent.status
7948:
Agent: enabled
Connection Type: remote
Protocol : rmi
Host : klara01
URL : service:jmx:rmi://klara01/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHVi
AAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxh
Mx4DAAB4cHciAAtVbmljYXN0UmVmMgEADjEwLjE2MS4xOTAuMTY3AADSonNyACdqYXZheC5ybWkuc3NsLlNzbFJNSUNsaWVudFNvY2tldEZhY3RvcnmMqrS7
gYUlDwIAAHhwdxeVBUcQ0oDc8Ok5v/0AAAFQ8Wb1poABAHg=
Properties :
com.sun.management.jmxremote.authenticate = false
com.sun.management.jmxremote.port = 7092
( Notice that eg. jmxremote.ssl defaults to true, and jmxremote.rmi.port defaults to 7092)
---------------------------
One could imagine another part of the output containing default values in use, something like
Properties :
com.sun.......
Defaults :
com.sun......
I have no idea if this is considered a bug or a feature, or how hard it would be to implement, and I realize that we might have thought about this for the original enhancement/CCC, where we never really specified the output in that detail.
Not sure if the issue should be a bug or an enh.
- clones
-
JDK-8023093 Add ManagementAgent.status diagnostic command
-
- Resolved
-