July 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5638) Remove the isOriginLocal from AbstractInvocationContext

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5638?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5638: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove the isOriginLocal from AbstractInvocationContext > ------------------------------------------------------- > > Key: ISPN-5638 > URL: https://issues.jboss.org/browse/ISPN-5638 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 8.0.0.Beta3 > > > We already have an origin field, we can use {{origin == null}} to check if the invocation is local. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5637) Use SingleKeyNonTxInvocationContext for remote non-tx writes

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5637?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5637: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use SingleKeyNonTxInvocationContext for remote non-tx writes > ------------------------------------------------------------ > > Key: ISPN-5637 > URL: https://issues.jboss.org/browse/ISPN-5637 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Remove commands always use a {{NonTxInvocationContext}}, even if they affect a single key. We should be able to use {{SingleKeyNonTxInvocationContext}} instead and avoid allocating a HashMap for the context entries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5639) Avoid creating a Callable instance for RPC timeout handling

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5639?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5639: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Avoid creating a Callable instance for RPC timeout handling > ----------------------------------------------------------- > > Key: ISPN-5639 > URL: https://issues.jboss.org/browse/ISPN-5639 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5640) Avoid a map lookup in SyncConfiguration.replTimeout()

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5640?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5640: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Avoid a map lookup in SyncConfiguration.replTimeout() > ----------------------------------------------------- > > Key: ISPN-5640 > URL: https://issues.jboss.org/browse/ISPN-5640 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5641) Reduce contention in JGroupsAddressCache

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5641?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5641: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Reduce contention in JGroupsAddressCache > ---------------------------------------- > > Key: ISPN-5641 > URL: https://issues.jboss.org/browse/ISPN-5641 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Avoid computeIfAbsent for existent entries, because it synchronizes on the entry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5645) JCache Processor does not update for a store-as-binary cache

by Patrick Ruckstuhl (JIRA)

Patrick Ruckstuhl created ISPN-5645: --------------------------------------- Summary: JCache Processor does not update for a store-as-binary cache Key: ISPN-5645 URL: https://issues.jboss.org/browse/ISPN-5645 Project: Infinispan Issue Type: Bug Components: JCache Affects Versions: 7.2.2.Final Reporter: Patrick Ruckstuhl If a cache that is configured with store-as-binary is used in jcache and a processor is invoked, the value will never be changed. The problem seems to be that the in JCache.invoke() V oldValue = skipCacheLoadCache.get(key); is retrieved and this is a different instance than retrieved in AbstractJCache.replace() with V current = existsCheckCache.get(key); so when if (isConditional && !current.equals(oldValue)) is called (and the value doesn't implement equal) they are never equal even though the value never changed. This is also related to ISPN-5504 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5504) Cache implementation for replace doesn't work with arrays

by Patrick Ruckstuhl (JIRA)

[ https://issues.jboss.org/browse/ISPN-5504?page=com.atlassian.jira.plugin.... ] Patrick Ruckstuhl commented on ISPN-5504: ----------------------------------------- I think it's even worse, the replace operation seems to require the VALUE to implement equals. > Cache implementation for replace doesn't work with arrays > --------------------------------------------------------- > > Key: ISPN-5504 > URL: https://issues.jboss.org/browse/ISPN-5504 > Project: Infinispan > Issue Type: Feature Request > Components: JCache > Affects Versions: 7.2.1.Final > Reporter: Christian Beikov > > The JCache/JSR107 implementation uses Object.equals for checking cache value equality. The replace function is therefore unable to handle array values. See https://github.com/infinispan/infinispan/blob/master/jcache/commons/src/m... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5644) IsMarshallableInterceptor doesn't check serializability of LockControlCommand keys

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5644?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5644: ------------------------------- Status: Open (was: New) > IsMarshallableInterceptor doesn't check serializability of LockControlCommand keys > ---------------------------------------------------------------------------------- > > Key: ISPN-5644 > URL: https://issues.jboss.org/browse/ISPN-5644 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.0.0.Beta3 > > > {{IsMarshallableInterceptor}} checks the serializability of the collection, which tries to serialize it the first time, and then it skips the serialization regardless of what keys are in it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5644) IsMarshallableInterceptor doesn't check serializability of LockControlCommand keys

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5644?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5644: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3612 > IsMarshallableInterceptor doesn't check serializability of LockControlCommand keys > ---------------------------------------------------------------------------------- > > Key: ISPN-5644 > URL: https://issues.jboss.org/browse/ISPN-5644 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.0.0.Beta3 > > > {{IsMarshallableInterceptor}} checks the serializability of the collection, which tries to serialize it the first time, and then it skips the serialization regardless of what keys are in it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5644) IsMarshallableInterceptor doesn't check serializability of LockControlCommand keys

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5644: ---------------------------------- Summary: IsMarshallableInterceptor doesn't check serializability of LockControlCommand keys Key: ISPN-5644 URL: https://issues.jboss.org/browse/ISPN-5644 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.0.0.Beta2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.0.0.Beta3 {{IsMarshallableInterceptor}} checks the serializability of the collection, which tries to serialize it the first time, and then it skips the serialization regardless of what keys are in it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2015