Thanks for your suggestion @Ryan.Paredez , I think giving jdk.jfr access to all unnamed modules is a security flaw, it would be appreciated if the module containing com.singularity.ee.agent.appagent could be a given a name in the next patch. Thanks! ... View more

To provide more context this is the exact error: ``` 'orgCache' threw exception; nested exception is java.lang.IllegalAccessError: class jdk.jfr.internal.SecuritySupport$$Lambda$1168/0x0000000100f17440 (in module jdk.jfr) cannot access class com.singularity.ee.agent.appagent.entrypoint.bciengine.FastMethodInterceptorDelegatorBoot (in unnamed module @0x1996cd68) because module jdk.jfr does not read unnamed module @0x1996cd68  ``` It seems `com.singularity.ee.agent.appagent.entrypoint.bciengine.FastMethodInterceptorDelegatorBoot` class (which comes from  AppD) has been placed inside an unnamed module, if that module could given a name, we could access it and deploy our service. ... View more

Hi @Ryan.Paredez , We are already using JDK8+JVM ver 22.12.0.  ... View more

Same issue in 22.12.0.34603, I can see the app agent is distinctly named 1.8-22.12.0.34603, is it because the app agent is only compatible with JDK 1.8 and not above? ... View more