Those messages might be coming from a slightly older version of SPLUNK4JMX, and in particular, attributes declared in these definitions : <mbean domain="java.lang" properties="type=GarbageCollector,name=ParNew"> <mbean domain="java.lang" properties="type=MemoryPool,name=CMS Old Gen"> You could actually delete these elements from the default config.xml file, and it won't affect the demo dashboards. These aren't really errors per say , but rather certain Mbean attributes aren't present or set in your target JVM. The default config file is only really supposed to be a guide/example of various scenarios (using simple/composite/tabular attributes) for you to then go and configure your own specific environment.ie: Different JVMs will have different Garbage Collectors, Memory Pool Names , ergo , different java.lang MBeans and attributes available. Best thing to do is to use a tool like JConsole to connect to your JVMs, browse the available MBeans and then make your config.xml file more specific to your particular JVM environment. ... View more