September 2019 - infinispan-issues

[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)

5 years, 3 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)

5 years, 3 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)

5 years, 3 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)

5 years, 3 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)

5 years, 3 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)

5 years, 3 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)

5 years, 3 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)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10408) Operator Docs: Version Compatibility

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10408?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10408: ------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #33) > Operator Docs: Version Compatibility > ------------------------------------ > > Key: ISPN-10408 > URL: https://issues.jboss.org/browse/ISPN-10408 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Break in Operator compatibility to support ServerNG > 0.x Operator remain server 9.x compatible. > 1.x Operators for ServerNG (Infinispan server 10.x) -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10620) BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and ignores overwriting

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10620?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10620: --------------------------------- Status: Open (was: New) > BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and ignores overwriting > -------------------------------------------------------------------------------------------------- > > Key: ISPN-10620 > URL: https://issues.jboss.org/browse/ISPN-10620 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > > The operations are held in a map keyed by name, so some overloaded operations like DefaultCahcheManager.startCache() and DefaultCahcheManager.startCache(String cacheName) are basically discarded unintentionally. > Also, the order of processing superclasses is wrong (reversed), so eventually overwritten operations are not correctly processed. The one in the superclass wins, so the overwrite is basically ignored. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019