MBeans view on JBoss/WildFly leads to OutOfMemoryError about javamelody HOT 2 CLOSED

Indeed.
I read in https://infinispan.org/docs/stable/titles/hibernate/hibernate.html :

Usually each entity hierarchy or collection has its own region

or in https://docs.jboss.org/author/display/ISPN53/Using%20Infinispan%20as%20JPA-Hibernate%20Second%20Level%20Cache%20Provider.html :

With the Infinispan cache provider, each entity/collection type gets each own cache instance

I choose option 3: always exclude the configurationAsProperties attribute, because some other users may have the same issue as you and the need to know the right configuration is not good. It is a bit sad for the few users who would be happy to see the configuration of infinispan caches (or other mbeans which have a configurationAsProperties attribute), but too much is too much for your case and we need to kill this issue.

from javamelody.

@evernat: Now there are already two properties that are suppressed: "password" and "configurationAsProperties".

Wouldn't it make sense to use these as default for a configuration option? I can imagine, that there are more sensitive properties, which some users would like to suppress.

from javamelody.