[JBoss JIRA] (ISPN-5482) JSR-107 - Provide mechanism to handle expiration events
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5482?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5482:
-----------------------------------------------
Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1222995|https://bugzilla.redhat.com/show_bug.cgi?id=1222995] from ON_QA to VERIFIED
> JSR-107 - Provide mechanism to handle expiration events
> --------------------------------------------------------
>
> Key: ISPN-5482
> URL: https://issues.jboss.org/browse/ISPN-5482
> Project: Infinispan
> Issue Type: Feature Request
> Components: JCache
> Reporter: Matej Čimbora
> Assignee: Gustavo Fernandes
> Fix For: 8.2.0.Alpha1, 8.0.3.Final
>
>
> Currently, expiration events are supported only by embedded mode & additionally require entry to be accessed in order to be created. This can lead to CacheEntryExpiredListener not being notified when an entry expires.
> Note: Not covered by TCK tests.
> Example:
> {code}
> @Test
> public void testExpiration(Method m) {
> Cache<String, String> cache1 = getCache1(m);
> Cache<String, String> cache2 = getCache2(m);
> TestExpiredListener listener = new TestExpiredListener();
> MutableCacheEntryListenerConfiguration conf1 = new MutableCacheEntryListenerConfiguration(FactoryBuilder.factoryOf(listener), null, false, false);
> cache1.registerCacheEntryListener(conf1);
> cache2.put("key1", "val1");
> sleep(5000);
> // Required by embedded JCache implementation to work
> assert cache1.get("key1") == null;
> // Failing for remote JCache implementation
> assertEquals(1, listener.invocationCount);
> }
> private static class TestExpiredListener implements CacheEntryExpiredListener, Serializable {
> private int invocationCount;
> @Override
> public void onExpired(Iterable iterable) throws CacheEntryListenerException {
> Iterator iterator = iterable.iterator();
> while (iterator.hasNext()) {
> iterator.next();
> invocationCount++;
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-5969) Number of max entries is not shown in cache statistics in mgmt console
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5969?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-5969:
-------------------------------------------
True, I have to see if we got this value from DMR because at the time we did not have it. Thanks [~jholusa]
> 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
[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-5972:
-------------------------------------------
[~jholusa] I am not doing anything special in UI, just displaying value I get from the underlying DMR. This is a cluster wide stat on this page and I don't recall right now if we should display numberOfNodes*numberOfEntries for REPL or just numberOfEntries from one cache. What is displayed on per node cache stat page ("Nodes" tab)? Would you please check DIST, INV and LOCAL and report back numbers you get? Thank you
> 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
[JBoss JIRA] (ISPN-5915) Displaying caches in management console doesn't detect non-TX cache correctly
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5915?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-5915:
--------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/30
> Displaying caches in management console doesn't detect non-TX cache correctly
> -----------------------------------------------------------------------------
>
> Key: ISPN-5915
> URL: https://issues.jboss.org/browse/ISPN-5915
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Alpha2
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
>
> Page "Caches" tab -> click on certain cache container: list of caches in that container is shown.
> Having cache configured e.g. like this:
> {code}
> <local-cache name="localCache" start="EAGER">
> <transaction mode="NONE"/>
> </local-cache>
> {code}
> However, in the UI, the cache is still marked as transactional. There is the "transactional" icon in the cache card and also when I click to the filter to show only TX caches, the cache is still displayed.
> It seems to me that the code only checks for presence of <transaction> element, but not it's "mode" attribute. If I set the cache without the <transaction> element, it's correctly recognized as non-TX cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-5999) Cannot create new node in mgmt console
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5999?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic resolved ISPN-5999.
---------------------------------------
Fix Version/s: 8.1.0.Final
Resolution: Done
> Cannot create new node in mgmt console
> --------------------------------------
>
> Key: ISPN-5999
> URL: https://issues.jboss.org/browse/ISPN-5999
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.CR1
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Fix For: 8.1.0.Final
>
>
> Page: Clusters -> select server group -> click "Add node".
> The page goes dark and redirects to log in page and it's not possible to proceed within the creation wizard.
> Note that this was working in 8.1.0.Beta1, started to appear in 8.1.0.CR1.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years