[
https://issues.jboss.org/browse/ISPN-4813?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-4813:
----------------------------------------
Vojtech, are you sure about clear? It appears to me that the issue are the result of how
size is calculated for different use cases. According to CI, the failures were introduced
by:
* HotRodRemoteCacheIT(distmode-udp).testPutAsync by ISPN-4736 and/or ISPN-4470 jiras.
* HotRodRemoteCacheIT(localmode-udp).testPutAsync and
HotRodRemoteCacheIT(replmode-udp).testPutAsync by ISPN-4820
I'll update once I have more info.
JMX returns wrong number of cache entries
-----------------------------------------
Key: ISPN-4813
URL:
https://issues.jboss.org/browse/ISPN-4813
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management, Remote Protocols, Server
Reporter: Vojtech Juranek
Assignee: Galder Zamarreño
Labels: testsuite_stability
Fix For: 7.0.0.Final
Number of cache entries ({{numberOfEntries}}) provided by JMX is wrong.
{{HotRodRemoteCacheIT#testPutAsyc}} fails with assert error (see bellow), because JMX
returns wrong number of entries in the cache. When debugging the test, number of entries
in the cache is correct (100 - obrained e.g. by {{cache.getBulk().size()}}), but JMX
return wrong number (100). Even on cleared cache JMX return that it contains 3 entries.
When the {{clear}} operation is called via JMX, JMX show correct number (0).
{noformat}
java.lang.AssertionError: expected:<100> but was:<103>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.infinispan.server.test.client.hotrod.AbstractRemoteCacheIT.testPutAsync(AbstractRemoteCacheIT.java:574)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)