[GR-55881] Issue with JDK Mission Control and Native Image Application Using JMX

[albertattard]

[GR-55881] Issue with JDK Mission Control and Native Image Application Using JMX

[fniephaus]

@roberttoyonaga is this something you could look into?

[albertattard]

Thank you very much @roberttoyonaga. I've noticed that some of the attributes that are exposed by the VM have the same issue. How can I address these too, please?

[selhagani]

Hi @albertattard , thank you for reporting this.

I just reproduced the issue and I confirm the issue you're facing.
We'll take a further look into this and I will keep you updated.

[albertattard]

Thank you @selhagani. Let me know if you require any further information.

[roberttoyonaga]

@fniephaus Yup, I can look into this issue.

[roberttoyonaga]

I was able to reproduce the issue. It looks like the problem is that you need to add serialization configuration for LocalDateTime.

Adding the below json in serialization-config.json inside the META-INF directory should fix the problem.

{
  "types":[

    {
      "name":"java.time.LocalDateTime"
    },
    {
      "name":"java.time.Ser"
    }
  ],
  "lambdaCapturingTypes":[
  ],
  "proxies":[
  ]
}

Running the Native Image Tracing Agent will help you generate the correct configuration automatically.

It's unfortunate that JMX requires extra configuration, but there isn't a good way of pre-configuring for all use-cases without greatly increasing image size (and remote JMX is already quite heavyweight). Maybe I'll update the JMX docs to suggest users run the tracing agent to generate their custom reflection configuration before using remote JMX.

[roberttoyonaga]

I think "java.lang.Double" needs to be added to the serialization config as well. All those "[N/A]" attribute values are doubles.

I'll open a PR to add java.lang.Double to the remote JMX Feature serialization config. It ought to be added there since its required for the OS platformMXBean.

Until that PR is integrated, you can use this for now:

{
  "types":[
    {
      "name":"java.time.LocalDateTime"
    },
    {
      "name":"java.lang.Double"
    },
    {
      "name":"java.time.Ser"
    }
  ],
  "lambdaCapturingTypes":[
  ],
  "proxies":[
  ]
}

[albertattard]

That's great @roberttoyonaga.

[roberttoyonaga]

I've put a PR up here: #9357

[fniephaus]

Thanks, Robert! I just took a look :)

[fniephaus]

This just got fixed on the main branch, and hopefully we can still backport it into the JDK 23 release.