Description of problem: ======================= - Unable to view the infinispan statistics from JBoss EAP 6 CLI. Version-Release number of selected component (if applicable): ============================================================== - JBoss EAP 6.4.x Steps to Reproduce: =================== 1) Take a fresh JBoss EAP 6.4.3 installation and consider `standalone-ha.xml` file. 2) Enable the infinispan statistics in the standalone-ha.xml file. Configuration looks as below: ----- <subsystem xmlns="urn:jboss:domain:infinispan:1.5"> : <cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan" statistics-enabled="true"> <transport lock-timeout="60000"/> <replicated-cache name="repl" mode="ASYNC" batching="true" statistics-enabled="true"> <file-store/> </replicated-cache> <replicated-cache name="sso" mode="SYNC" batching="true"/> <distributed-cache name="dist" l1-lifespan="0" mode="ASYNC" batching="true"> <file-store/> </distributed-cache> </cache-container> : </subsystem> ----- 3) Start the JBoss server with `standalone-ha.xml` file. 4) Deploy the cluster web application and hit the application. 5) and check the infinispan statistics by using the below cli command: ----- /subsystem=infinispan/cache-container=web/replicated-cache=repl/:read-resource(include-runtime=true) ----- 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change. Actual results: =============== - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed. Expected results: ================= - There should be a change in the runtime parameters values. Additional info: ================= - I can see the expected result from the jconsole statistics. jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics. - Found a JDG bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1210176
The underlying issue is that the cache instance used to store web session data for a deployed web application has no corresponding runtime management resource from which to obtain metrics. See https://issues.jboss.org/browse/WFLY-5685
Closing as this is a feature not a bug, see https://issues.jboss.org/browse/WFLY-5685