September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-7624) Change CacheLoaderInterceptor to ignore in memory for certain operations when passivation is not enabled

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-7624?page=com.atlassian.jira.plugin.... ] Will Burns updated ISPN-7624: ----------------------------- Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34) > Change CacheLoaderInterceptor to ignore in memory for certain operations when passivation is not enabled > -------------------------------------------------------------------------------------------------------- > > Key: ISPN-7624 > URL: https://issues.jboss.org/browse/ISPN-7624 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > CacheLoader currently reads all in memory entries and then the store for bulk operations. This can be changed to only load from the store when passivation is not used as it should contain all entries that aren't in memory. > The only issue is that if Flag.SKIP_CACHE_STORE was used on a write. In this case we could store a boolean in the interceptor so that if this Flag is ever used we always do both. Very few users use this Flag and it should improve performance a bit and entries should be seen more consistently. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromise

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10621?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10621: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7318 > NullPointerException in CompositeLockPromise > -------------------------------------------- > > Key: ISPN-10621 > URL: https://issues.jboss.org/browse/ISPN-10621 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.CR3 > > > The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromise

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10621?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10621: ------------------------------- Affects Version/s: 10.0.0.CR2 > NullPointerException in CompositeLockPromise > -------------------------------------------- > > Key: ISPN-10621 > URL: https://issues.jboss.org/browse/ISPN-10621 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.CR3 > > > The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromise

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10621?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10621: ------------------------------- Fix Version/s: 10.0.0.CR3 > NullPointerException in CompositeLockPromise > -------------------------------------------- > > Key: ISPN-10621 > URL: https://issues.jboss.org/browse/ISPN-10621 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.CR3 > > > The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromise

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10621?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10621: ------------------------------- Summary: NullPointerException in CompositeLockPromise (was: NullPointerException in CompositeLockPromite) > NullPointerException in CompositeLockPromise > -------------------------------------------- > > Key: ISPN-10621 > URL: https://issues.jboss.org/browse/ISPN-10621 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromite

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10621?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10621: ------------------------------- Status: Open (was: New) > NullPointerException in CompositeLockPromite > -------------------------------------------- > > Key: ISPN-10621 > URL: https://issues.jboss.org/browse/ISPN-10621 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromite

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10621?page=com.atlassian.jira.plugin... ] Work on ISPN-10621 started by Pedro Ruivo. ------------------------------------------ > NullPointerException in CompositeLockPromite > -------------------------------------------- > > Key: ISPN-10621 > URL: https://issues.jboss.org/browse/ISPN-10621 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10600) Create empty XSiteStateTransferManager and related classes

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10600?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10600: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7316 > Create empty XSiteStateTransferManager and related classes > ---------------------------------------------------------- > > Key: ISPN-10600 > URL: https://issues.jboss.org/browse/ISPN-10600 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.CR3 > > > When a cache doesn't have cross-site replication enabled, it can instantiate empty implementation of {{XSiteStateTransferManager}}, {{XSiteStateConsumer}} and {{XSiteStateProvider}} to save some memory and avoid registering uneeded listeners. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10621) NullPointerException in CompositeLockPromite

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-10621: ---------------------------------- Summary: NullPointerException in CompositeLockPromite Key: ISPN-10621 URL: https://issues.jboss.org/browse/ISPN-10621 Project: Infinispan Issue Type: Bug Reporter: Pedro Ruivo Assignee: Pedro Ruivo The {{CompositeLockPromise}} always assume {{timeoutTask}} is non-null. However, it isn't the case for timeout=0 (i.e. tryLock behavior) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10600) Create empty XSiteStateTransferManager and related classes

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10600?page=com.atlassian.jira.plugin... ] Pedro Ruivo commented on ISPN-10600: ------------------------------------ I went for a different approach. {{XSiteStateConsumer}} is always instantiated because of the active-passive xsite scenario. Even without xsite enabled, a cache can receive state from a remote site. The other related classes are instantiated only if xsite is enabled: * {{XSiteAdminOperations}}, that depends on: ** {{BackupSender}} ** {{XSiteStateTransferManager}}, that depends on *** {{XSiteStateProvider}} > Create empty XSiteStateTransferManager and related classes > ---------------------------------------------------------- > > Key: ISPN-10600 > URL: https://issues.jboss.org/browse/ISPN-10600 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.CR3 > > > When a cache doesn't have cross-site replication enabled, it can instantiate empty implementation of {{XSiteStateTransferManager}}, {{XSiteStateConsumer}} and {{XSiteStateProvider}} to save some memory and avoid registering uneeded listeners. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 6 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 September 2019