I have project with Hazelcast & Ignite dependencies. And Ignite actually not started/used (there is property that switches Ignite & Hazelcast at app start). A Hazelcast's client is used which connects to the cluster. Used for storage (not cache).
It's okay when javamelody is disabled. But when I try to use javamelody and open a webpage. Ignite starts (seems like even not a just client). The Hazelcast cache manager tries to start and eventually throws an exception (not configured, so everything is fine). So, actually javamelody do not works at this case.
Do you know some hack to disable starting of Ignite/Hazelcast cache managers when javamelody enabled?
It has a long history: https://github.com/javamelody/javamelody/issues/858 https://github.com/javamelody/javamelody/issues/962
Maybe you can try to put Hz/Ignite in a different class loader than Java Melody?