AnsweredAssumed Answered

JMX metrics path exposion

Question asked by jkutes1.1 on Oct 1, 2013
Latest reply on Oct 3, 2013 by jkutes1.1
Hi,
I'm looking for fix/workaround to avoid metrics path explosion for our EHCACHE JMX metrics.
Since our non prod instances get restarted often and with every restart ehcache manager keep on changing the name (append 8 chars "@xxxxxxx) after while we end up with jmx metric path explosion and need to clean up SmartStor.
Here is the example
JMX|net.sf.ehcache|CacheManager=net.sf.ehcache.CacheManager@3897bba|name=ImageCache|type=CacheStatistics
CacheHits
0.0
JMX|net.sf.ehcache|CacheManager=net.sf.ehcache.CacheManager@2f11e6e|name=ImageCache|type=CacheStatistics
CacheHits
0.0
JMX|net.sf.ehcache|CacheManager=net.sf.ehcache.CacheManager@27129a7|name=ImageCache|type=CacheStatistics
CacheHits
0.0
JMX|net.sf.ehcache|CacheManager=net.sf.ehcache.CacheManager@261a7a5|name=ImageCache|type=CacheStatistics
CacheHits
0.0
JMX|net.sf.ehcache|CacheManager=net.sf.ehcache.CacheManager@1db6f5f|name=ImageCache|type=CacheStatistics
CacheHits
0.0
JMX|net.sf.ehcache|CacheManager=net.sf.ehcache.CacheManager@1c835b7|name=ImageCache|type=CacheStatistics
CacheHits
0.0

Would anybody have any experience with Wily's JMX settings for ehcache, or similar issue?

Appreciate.

Outcomes