[infinispan-issues] [JBoss JIRA] (ISPN-4813) JMX returns wrong number of cache entries

[Vojtech Juranek (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009762#comment-13009762 ] 

Vojtech Juranek commented on ISPN-4813:
---------------------------------------

This is caused by HotRod {{clear}} request, which actually doesn't call {{clear()}} method on data container and thus some entries survive there. JMX then reports actual number of entries in data container.

> 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
>            Reporter: Vojtech Juranek
>            Assignee: Mircea Markus
>
> 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)