NotCompliantMBeanException during cache creation

[Alan Bateman]

On 16/03/2025 02:12, ioi.lam at oracle.com wrote:
> Could you send the exact command-line that causes the error? If you 
> can share a self-contain reproducible test case, that would be great!
>
> Looking from the stack trace:
>
>     at 
> jdk.management.agent/sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:542)
>     at 
> jdk.management.agent/jdk.internal.agent.Agent.startLocalManagementAgent(Agent.java:316)
>     at 
> jdk.management.agent/jdk.internal.agent.Agent.startAgent(Agent.java:448)
>     at 
> jdk.management.agent/jdk.internal.agent.Agent.startAgent(Agent.java:601)
>
> It looks like you might have specified a Java agent in the "java 
> -XX:AOTMode=create ...." command line. Can you try removing that and 
> see if it works?

I assume it's something started with -Dcom.sun.management=... to start 
the JMX agent. This sets in motion the registration of management beans 
and the JMX introspector machinery that looks at annotations and causes 
Proxy classes to be generated into dynamic modules.

Ioi - I suspect the restriction on creating dynamic modules in the dump 
phase may be too restrictive. The full module graph dumping should only 
be concerned with the boot layer.

-Alan