]
Paul Ferraro commented on WFLY-5627:
------------------------------------
[~lpeano] The routing information is stored in a cache instance per server (i.e. undertow
"server"), named using the name of that server (e.g. <server
name="default-server">...</server>. I'm not sure why statistics
from this cache would be of any interest.
Unable to view the infinispan statistics from CLI
-------------------------------------------------
Key: WFLY-5627
URL:
https://issues.jboss.org/browse/WFLY-5627
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Chao Wang
Assignee: Paul Ferraro
When I investigated
https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its
scenario with WildFly as:
{noformat}
Steps to Reproduce:
===================
1) Build latest Wildfly master 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:4.0">
<cache-container name="server" aliases="singleton
cluster" module="org.wildfly.clustering.server"
default-cache="default">
<transport lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC">
<transaction mode="BATCH"/>
</replicated-cache>
</cache-container>
<cache-container name="web"
module="org.wildfly.clustering.web.infinispan" default-cache="dist"
statistics-enabled="true">
<transport lock-timeout="60000"/>
<distributed-cache name="dist"
statistics-enabled="true" mode="ASYNC" l1-lifespan="0"
owners="2">
<locking isolation="REPEATABLE_READ"/>
<transaction mode="BATCH"/>
<file-store/>
</distributed-cache>
</cache-container>
-----
3) Start the 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/distributed-cache=dist: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.
{noformat}
It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit
https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes
such difference. Once I revert this commit, I can see dynamic statistics change in CLI
operation.