[JBoss JIRA] (ISPN-5939) RemoteListenerWithDslFilterTest.testEventFilter and NonIndexedCacheRemoteListenerWithDslFilterTest.testEventFilter fail randomly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5939?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5939:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1279877|https://bugzilla.redhat.com/show_bug.cgi?id=1279877] from ON_QA to VERIFIED
> RemoteListenerWithDslFilterTest.testEventFilter and NonIndexedCacheRemoteListenerWithDslFilterTest.testEventFilter fail randomly
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-5939
> URL: https://issues.jboss.org/browse/ISPN-5939
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Reporter: Roman Macor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta2, 8.0.2.Final
>
>
> RemoteListenerWithDslFilterTest.testEventFilter and NonIndexedCacheRemoteListenerWithDslFilterTest.testEventFilter fail randomly with:
> Error Message
> expected:<2> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<2> but was:<0>
> 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.client.hotrod.event.RemoteListenerWithDslFilterTest.testEventFilter(RemoteListenerWithDslFilterTest.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5969) Number of max entries is not shown in cache statistics in mgmt console
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-5969?page=com.atlassian.jira.plugin.... ]
Jiří Holuša updated ISPN-5969:
------------------------------
Description:
Page: Caches -> select cache container -> select some cache
Even when the maximum number of entries is specified for the cache and management console correctly marks it as "Bounded", the cache statistics field "Max capacity" is still with value "TODO".
Also the progress bar below it seems to be not working yet.
was:
Page: Caches -> select cache container -> select some cache
Even when the maximum number of entries is specified for the cache and management console correctly marks it as "Bounded", the cache statistics field "Max capacity" is still with value "TODO".
> Number of max entries is not shown in cache statistics in mgmt console
> ----------------------------------------------------------------------
>
> Key: ISPN-5969
> URL: https://issues.jboss.org/browse/ISPN-5969
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
>
> Page: Caches -> select cache container -> select some cache
> Even when the maximum number of entries is specified for the cache and management console correctly marks it as "Bounded", the cache statistics field "Max capacity" is still with value "TODO".
> Also the progress bar below it seems to be not working yet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console
by Jiří Holuša (JIRA)
Jiří Holuša created ISPN-5972:
---------------------------------
Summary: Number of entries not working correctly in cache statistics in mgmt console
Key: ISPN-5972
URL: https://issues.jboss.org/browse/ISPN-5972
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 8.1.0.Beta1
Reporter: Jiří Holuša
Assignee: Vladimir Blagojevic
Page: Caches -> select cache container -> select cache.
Configuration of the cache: replicated cache, 2 nodes in the domain
In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5971) Longer cache name overflows its div in mgmt console
by Jiří Holuša (JIRA)
Jiří Holuša created ISPN-5971:
---------------------------------
Summary: Longer cache name overflows its div in mgmt console
Key: ISPN-5971
URL: https://issues.jboss.org/browse/ISPN-5971
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 8.1.0.Beta1
Reporter: Jiří Holuša
Assignee: Vladimir Blagojevic
Priority: Minor
Page: Caches -> select cache container
When having cache with a longer name, e.g. replicatedCacheForStatisticsTesting, it overflows its tab. The tabs are probably fixed size. This might be an issue which requires more discussion what is correct solution, if increase the fixed size or make it flexible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5970) Value os READ/WRITE ration field in cache statistics in mgmt console is not aligned
by Jiří Holuša (JIRA)
Jiří Holuša created ISPN-5970:
---------------------------------
Summary: Value os READ/WRITE ration field in cache statistics in mgmt console is not aligned
Key: ISPN-5970
URL: https://issues.jboss.org/browse/ISPN-5970
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 8.1.0.Beta1
Reporter: Jiří Holuša
Assignee: Vladimir Blagojevic
Priority: Minor
Page: Caches -> select cache container -> select cache
In the "Cache content" tab, there is "READ/WRITE ration" field. It's value is not aligned with the others in the same tab. When I look at the HTML code, there is an extra empty <td> element causing this problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-5969) Number of max entries is not shown in cache statistics in mgmt console
by Jiří Holuša (JIRA)
Jiří Holuša created ISPN-5969:
---------------------------------
Summary: Number of max entries is not shown in cache statistics in mgmt console
Key: ISPN-5969
URL: https://issues.jboss.org/browse/ISPN-5969
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 8.1.0.Beta1
Reporter: Jiří Holuša
Assignee: Vladimir Blagojevic
Page: Caches -> select cache container -> select some cache
Even when the maximum number of entries is specified for the cache and management console correctly marks it as "Bounded", the cache statistics field "Max capacity" is still with value "TODO".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months