[JBoss JIRA] (ISPN-7935) Document Server Tasks
by Vittorio Rigamonti (JIRA)
[ https://issues.jboss.org/browse/ISPN-7935?page=com.atlassian.jira.plugin.... ]
Vittorio Rigamonti updated ISPN-7935:
-------------------------------------
Fix Version/s: 9.0.4.Final
(was: 9.0.3.Final)
> Document Server Tasks
> ---------------------
>
> Key: ISPN-7935
> URL: https://issues.jboss.org/browse/ISPN-7935
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server, Tasks
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 9.1.0.Final, 9.0.4.Final
>
>
> There's literally no documentation on using ServerTask. They're very powerful and we should promote them more since they can act as a stop gap solution for any missing features in HR client.
> I'll add documentation for ServerTasks once Infinispan can execute ServerTasks fine, even if they're POJOs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7954) Cache.getCacheEntry clears created/lastUsed times before returning
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7954?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-7954:
------------------------------------
Created time seems useful, especially for rolling upgrades. OTOH I don't think there's a way to create an entry with a specific timestamp, either.
> Cache.getCacheEntry clears created/lastUsed times before returning
> ------------------------------------------------------------------
>
> Key: ISPN-7954
> URL: https://issues.jboss.org/browse/ISPN-7954
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.1.Final, 9.1.0.Beta1
> Reporter: William Burns
>
> While writing a test for ISPN-7952 I found that due to the layers of wrapping and transformations of cache entry objects that the created and last used times will get cleared and set to 0. Do we care about user getting this data, and actually lastUsed would probably be the current time as it was just accessed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7954) Cache.getCacheEntry clears created/lastUsed times before returning
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7954?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-7954:
-----------------------------------
Last used set to current time does not sound too useful, unless you have some aversion against calling System.currentTimeMillis() directly :) I would rather provide last access time and update that only after that. If it's not too much fuss.
> Cache.getCacheEntry clears created/lastUsed times before returning
> ------------------------------------------------------------------
>
> Key: ISPN-7954
> URL: https://issues.jboss.org/browse/ISPN-7954
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.1.Final, 9.1.0.Beta1
> Reporter: William Burns
>
> While writing a test for ISPN-7952 I found that due to the layers of wrapping and transformations of cache entry objects that the created and last used times will get cleared and set to 0. Do we care about user getting this data, and actually lastUsed would probably be the current time as it was just accessed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7590) Entry version history
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7590?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-7590:
------------------------------
Summary: Entry version history (was: Proper command retry handling)
> Entry version history
> ---------------------
>
> Key: ISPN-7590
> URL: https://issues.jboss.org/browse/ISPN-7590
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 9.0.0.CR2
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Labels: consistency
>
> This is an umbrella JIRA to change the way how we deal with retries after topology change.
> Please link any outstanding issues that refer to incorrect return values of command during topology change.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7820) Document store-by-reference effects in functional commands
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7820?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-7820:
------------------------------
Status: Open (was: New)
> Document store-by-reference effects in functional commands
> ----------------------------------------------------------
>
> Key: ISPN-7820
> URL: https://issues.jboss.org/browse/ISPN-7820
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core, Transactions
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
>
> In transactional mode, functional read write command loads the value into the context without making a defensive copy. Then, the function is applied directly on that value, exposing uncommitted changes to all other threads. Rollback is ineffective, the value is already changed.
> There are no tests for rollback in FunctionalTxInMemoryTest.
> Reproducer:
> {code:java}
> @Test
> public void testValueInContextIsACopy() throws Exception {
> Object key = getKeyForCache(cache(0, DIST), cache(1, DIST));
> cache(0, DIST).put(key, new ArrayList());
> tm.begin();
> // nasty cast
> FunctionalMap.ReadWriteMap<Object, List> otherRw = (FunctionalMap.ReadWriteMap) rw;
> otherRw.eval(key, (Serializable & Function<EntryView.ReadWriteEntryView<Object, List>, Object>) view -> {
> List list = view.get();
> list.add("woohoo");
> view.set(list);
> return null;
> }).join();
> tm.rollback();
> assertEquals(new ArrayList(), cache(0, DIST).get(key));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7820) Document store-by-reference effects in functional commands
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7820?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-7820:
------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5222
> Document store-by-reference effects in functional commands
> ----------------------------------------------------------
>
> Key: ISPN-7820
> URL: https://issues.jboss.org/browse/ISPN-7820
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core, Transactions
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
>
> In transactional mode, functional read write command loads the value into the context without making a defensive copy. Then, the function is applied directly on that value, exposing uncommitted changes to all other threads. Rollback is ineffective, the value is already changed.
> There are no tests for rollback in FunctionalTxInMemoryTest.
> Reproducer:
> {code:java}
> @Test
> public void testValueInContextIsACopy() throws Exception {
> Object key = getKeyForCache(cache(0, DIST), cache(1, DIST));
> cache(0, DIST).put(key, new ArrayList());
> tm.begin();
> // nasty cast
> FunctionalMap.ReadWriteMap<Object, List> otherRw = (FunctionalMap.ReadWriteMap) rw;
> otherRw.eval(key, (Serializable & Function<EntryView.ReadWriteEntryView<Object, List>, Object>) view -> {
> List list = view.get();
> list.add("woohoo");
> view.set(list);
> return null;
> }).join();
> tm.rollback();
> assertEquals(new ArrayList(), cache(0, DIST).get(key));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months