JDK-8176314 : JMX: RuntimeMXBean support for monitoring modular runtime information
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 9
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-03-07
  • Updated: 2024-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
Relates :  
JDK-8189091 - MBean access to the PID
Description
It would be useful for a JMX-compliant tool to show the modular runtime information such as the observable and resolved modules in the target VM.

See http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-March/011553.html
Comments
As pointed out by Alan and Mandy on the mailing list [1,2] exposing jdk.internal.module.ModuleBootstrap.finder() isn't a good solution for this problem because it won't work in remote scenarios. [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-March/011568.html [2] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-March/011569.html
09-03-2017
I think this could be easily achieved by exposing jdk.internal.module.ModuleBootstrap.finder() trough the RuntimeMXBean. We could for example add a method getObservableModulesFinder()" to RuntimeMXBean which returns jdk.internal.module.ModuleBootstrap.finder(). The question only is if this is still realistic for Java 9 or if it has to be postponed to Java 10?
08-03-2017