JDK-8175907 : JMX should be expanded to know about physical quantities and units of measurement.
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: javax.management
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-02-27
  • Updated: 2019-07-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Blocks :  
Relates :  
Description
Currently tools cannot be aware about the physical quantities and units of measurement for JMX attributes. The JMC console uses a client side lookup for such metadata, and allows users to set these properties for arbitrary attributes. That is of course a very nice feature, but it would be even better if the developer of the MBeans could provide metadata explaining what physical quantity (e.g. length) and unit of measurement (e.g. meters) was used for a certain attribute.

This information should probably be provided in a typed way from the MBeanAttributeInfo, but could also be provided by establishing a convention for how to store the metadata in the Descriptor.

See JSR 363.
Comments
Do we have an implementation of JSR 363 in JDK9. If not, then only way to provide information that can be serialized to JSR 363 types is to provide String that can be parsed into JSR 363 types. Enforcing such a constraint is not user-friendly and validation of such a constraint is also non-trivial.
28-02-2017

I will open a separate bug for making j.l.m. use this.
27-02-2017