August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5677?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-5677: -------------------------------------- Assignee: Galder Zamarreño > HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) > ---------------------------------------------------------------------- > > Key: ISPN-5677 > URL: https://issues.jboss.org/browse/ISPN-5677 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Shay Matasaro > Assignee: Galder Zamarreño > > given the following HR client code > NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); > System.out.println(f1.get(10,TimeUnit.MINUTES)); > NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); > System.out.println(f2.get(10,TimeUnit.MINUTES)); > both prints print null, where the second one should print "1" > only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5677?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5677: ----------------------------------- Status: Open (was: New) > HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) > ---------------------------------------------------------------------- > > Key: ISPN-5677 > URL: https://issues.jboss.org/browse/ISPN-5677 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Shay Matasaro > Assignee: Galder Zamarreño > > given the following HR client code > NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); > System.out.println(f1.get(10,TimeUnit.MINUTES)); > NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); > System.out.println(f2.get(10,TimeUnit.MINUTES)); > both prints print null, where the second one should print "1" > only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5677?page=com.atlassian.jira.plugin.... ] Work on ISPN-5677 started by Galder Zamarreño. ---------------------------------------------- > HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) > ---------------------------------------------------------------------- > > Key: ISPN-5677 > URL: https://issues.jboss.org/browse/ISPN-5677 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Shay Matasaro > Assignee: Galder Zamarreño > > given the following HR client code > NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); > System.out.println(f1.get(10,TimeUnit.MINUTES)); > NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); > System.out.println(f2.get(10,TimeUnit.MINUTES)); > both prints print null, where the second one should print "1" > only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5664) Null is returned for a not expired entry in Hot Rod client

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5664?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5664: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1253052|https://bugzilla.redhat.com/show_bug.cgi?id=1253052] from NEW to POST > Null is returned for a not expired entry in Hot Rod client > ---------------------------------------------------------- > > Key: ISPN-5664 > URL: https://issues.jboss.org/browse/ISPN-5664 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > For a mortal entry (lifespan > -1), overwriting it with lifespan=-1 (make it immortal) unexpectedly removes the entry like follows. > ~~~ > cache.put(key, "value1", 100, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value1" > cache.put(key, "value2", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns null, expected "value2" > cache.put(key, "value3", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value3" > ~~~ > In library mode, the 2nd get returns non-null as expected. The same behaviour is observed for a transient (maxIdle > -1) entry also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5664) Null is returned for a not expired entry in Hot Rod client

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5664?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5664: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1243671, https://bugzilla.redhat.com/show_bug.cgi?id=1253052 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1243671) > Null is returned for a not expired entry in Hot Rod client > ---------------------------------------------------------- > > Key: ISPN-5664 > URL: https://issues.jboss.org/browse/ISPN-5664 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > For a mortal entry (lifespan > -1), overwriting it with lifespan=-1 (make it immortal) unexpectedly removes the entry like follows. > ~~~ > cache.put(key, "value1", 100, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value1" > cache.put(key, "value2", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns null, expected "value2" > cache.put(key, "value3", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value3" > ~~~ > In library mode, the 2nd get returns non-null as expected. The same behaviour is observed for a transient (maxIdle > -1) entry also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5674) A DistributedCallable with defined keys is executing on local node , even if the local node does not own any of the keys

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5674?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-5674. --------------------------------- Resolution: Rejected This is the intended behavior is that the running node(s) is determined by the keys passed in. They are not used for any other determination. > A DistributedCallable with defined keys is executing on local node , even if the local node does not own any of the keys > ------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5674 > URL: https://issues.jboss.org/browse/ISPN-5674 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 8.0.0.Beta3, 7.2.4.Final > Reporter: Tristan Tarrant > Assignee: William Burns > > A DistributedCallable which is submitted with defined keys is executing on local node , even if the local node does not own any of the keys -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5676) EntryRetrievalCommand must enlist the transaction

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5676?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5676: -------------------------------- Fix Version/s: 8.0.0.CR1 7.2.5.Final > EntryRetrievalCommand must enlist the transaction > ------------------------------------------------- > > Key: ISPN-5676 > URL: https://issues.jboss.org/browse/ISPN-5676 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.4.Final > Reporter: Radim Vansa > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > When entries are read in transactional cache through cache.filterEntries() and there are no other operations in this transaction, new LocalTransaction is created and registered in the TransactionTable but this is never enlisted; TxInterceptor.visitEntryRetrievalCommand does not enlist it. > Since unregistration from TransactionTable relies on enlistment, the LocalTransaction stays there until it is cleaned up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5676) EntryRetrievalCommand must enlist the transaction

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5676?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5676: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3647, https://github.com/infinispan/infinispan/pull/3646 > EntryRetrievalCommand must enlist the transaction > ------------------------------------------------- > > Key: ISPN-5676 > URL: https://issues.jboss.org/browse/ISPN-5676 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.4.Final > Reporter: Radim Vansa > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > When entries are read in transactional cache through cache.filterEntries() and there are no other operations in this transaction, new LocalTransaction is created and registered in the TransactionTable but this is never enlisted; TxInterceptor.visitEntryRetrievalCommand does not enlist it. > Since unregistration from TransactionTable relies on enlistment, the LocalTransaction stays there until it is cleaned up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5677?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5677: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1252986 > HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) > ---------------------------------------------------------------------- > > Key: ISPN-5677 > URL: https://issues.jboss.org/browse/ISPN-5677 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Shay Matasaro > > given the following HR client code > NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); > System.out.println(f1.get(10,TimeUnit.MINUTES)); > NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); > System.out.println(f2.get(10,TimeUnit.MINUTES)); > both prints print null, where the second one should print "1" > only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by Shay Matasaro (JIRA)

Shay Matasaro created ISPN-5677: ----------------------------------- Summary: HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) Key: ISPN-5677 URL: https://issues.jboss.org/browse/ISPN-5677 Project: Infinispan Issue Type: Bug Affects Versions: 6.0.2.Final Reporter: Shay Matasaro given the following HR client code NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); System.out.println(f1.get(10,TimeUnit.MINUTES)); NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); System.out.println(f2.get(10,TimeUnit.MINUTES)); both prints print null, where the second one should print "1" only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2015