javax.management.JMX.createProxy is not implemented in native mode

[jamesnetherton]

Describe the bug

In the Quarkus Core there is this substitution for javax.management.JMX.createProxy:

https://github.com/quarkusio/quarkus/blob/1ba5ca13b724079df3e63b6c14df212a4b5a5542/core/runtime/src/main/java/io/quarkus/runtime/graal/Target_javax_management_JMX.java

I wonder if this could be removed or be made conditional based on whether native JMX support is enabled?

Camel has a comprehensive JMX based management layer and there's a few code paths that trigger activation of javax.management.JMX. Which leads to runtime exceptions like this:

java.lang.IllegalStateException: Not Implemented in native mode
	at java.management@21.0.2/javax.management.JMX.createProxy(JMX.java:19)
	at java.management@21.0.2/javax.management.JMX.newMBeanProxy(JMX.java:216)
	at java.management@21.0.2/javax.management.MBeanServerInvocationHandler.newProxyInstance(MBeanServerInvocationHandler.java:240)
	at org.apache.camel.management.DefaultManagementAgent.newProxyClient(DefaultManagementAgent.java:396)
	at org.apache.camel.management.mbean.ManagedCamelContext.dumpRoutesStatsAsXml(ManagedCamelContext.java:646)

I tested with removing the substitution and my previously failing JMX operation invocations started working fine.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Mandrel or GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @Karm (native-image), @galderz (native-image), @zakkak (native-image)

[geoand]

Does native image support JMX now?

[zakkak]

Does native image support JMX now?

Yes, there should be (at least partial) support for JMX.

@roberttoyonaga will probably be able to provide more info on the potential limitations.

[roberttoyonaga]

Yes, partial Native Image support for remote JMX connections has been added. However, currently only platform MXBeans and standard MBeans are supported (not model or dynamic mbeans). With respect to platform MXbeans, not all attributes and functionality is implemented (much is, but there are still things missing like accessing ThreadInfo from the ThreadMXBean).

JMX.createProxy gets called from JMX.newMBeanProxy, which I believe only accepts standard MBeans. So I think what you are trying to do should work. Maybe this Quarkus substitution is out-of-date and is no longer necessary.

Let me do a check for myself, then I will follow up again here.

The docs are here if you haven't found them already.

[roberttoyonaga]

I tried out using JMX.newMBeanProxy with a sample client/server (both native images). I can confirm that it works as expected with a standardMBean as long as the corresponding dynamic proxy reflection configuration is provided. I believe that the Quarkus substitution is no longer needed.

[zakkak]

Fixed by #46592