March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7632) Remove useEagerLocking configuration

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7632: ---------------------------------- Summary: Remove useEagerLocking configuration Key: ISPN-7632 URL: https://issues.jboss.org/browse/ISPN-7632 Project: Infinispan Issue Type: Bug Components: Configuration, Core Affects Versions: 9.0.0.CR2 Reporter: Dan Berindei Assignee: Pedro Ruivo Fix For: 9.0.0.Final The {{useEagerLocking}} configuration was deprecated in version 5.1, we can safely remove it in 9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7632) Remove useEagerLocking configuration

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7632?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7632: ------------------------------- Status: Open (was: New) > Remove useEagerLocking configuration > ------------------------------------ > > Key: ISPN-7632 > URL: https://issues.jboss.org/browse/ISPN-7632 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 9.0.0.Final > > > The {{useEagerLocking}} configuration was deprecated in version 5.1, we can safely remove it in 9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7631) Cache.entrySet() entries don't implement Map.Entry.equals() correctly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7631?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7631: ------------------------------------ This also applies to entries returned by {{AdvancedCache.getCacheEntry()}}. Since it also returns a {{Map.Entry}} implementation, I should be able to check the value of an entry with {code:java} new AbstractMap.SimpleEntry("k", "v").equals(cache.getAdvancedCache().getCacheEntry("k")) {code} > Cache.entrySet() entries don't implement Map.Entry.equals() correctly > --------------------------------------------------------------------- > > Key: ISPN-7631 > URL: https://issues.jboss.org/browse/ISPN-7631 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > > The {{Map.Entry.equals()}} javadoc says "Returns true if the given object is also a map entry and the two entries represent the same mapping.", meaning any other metadata stored in cache entries (e.g. lifespan) must be ignored for the purpose of checking equality. In other words, this code should work regardless of what entries are stored in the cache or in the invocation context: > {code:java} > cache.entrySet().contains(new AbstractMap.SimpleEntry("k", "v")) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7631) Cache.entrySet() entries don't implement Map.Entry.equals() correctly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7631?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7631: ------------------------------- Status: Open (was: New) > Cache.entrySet() entries don't implement Map.Entry.equals() correctly > --------------------------------------------------------------------- > > Key: ISPN-7631 > URL: https://issues.jboss.org/browse/ISPN-7631 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > > The {{Map.Entry.equals()}} javadoc says "Returns true if the given object is also a map entry and the two entries represent the same mapping.", meaning any other metadata stored in cache entries (e.g. lifespan) must be ignored for the purpose of checking equality. In other words, this code should work regardless of what entries are stored in the cache or in the invocation context: > {code:java} > cache.entrySet().contains(new AbstractMap.SimpleEntry("k", "v")) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7631) Cache.entrySet() entries don't implement Map.Entry.equals() correctly

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7631: ---------------------------------- Summary: Cache.entrySet() entries don't implement Map.Entry.equals() correctly Key: ISPN-7631 URL: https://issues.jboss.org/browse/ISPN-7631 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.CR2 Reporter: Dan Berindei Assignee: Pedro Ruivo The {{Map.Entry.equals()}} javadoc says "Returns true if the given object is also a map entry and the two entries represent the same mapping.", meaning any other metadata stored in cache entries (e.g. lifespan) must be ignored for the purpose of checking equality. In other words, this code should work regardless of what entries are stored in the cache or in the invocation context: {code:java} cache.entrySet().contains(new AbstractMap.SimpleEntry("k", "v")) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7614) Disabling a store doesn't stop it

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7614?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7614. -------------------------------- Resolution: Done > Disabling a store doesn't stop it > --------------------------------- > > Key: ISPN-7614 > URL: https://issues.jboss.org/browse/ISPN-7614 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final > > > When disabling a store via {{PersistenceManager.disableStore(...)}}, the store is removed from the list of loaders/writers, but its {{stop()}} method is not called, so buffers may not be flushed. > {{AsyncCacheWriter}} will also leak the {{AsyncStoreCoordinator}} thread if {{stop()}} is not called, and this thread leak is visible when running {{ClassLoaderManagerDisablingTest}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7630) Getting coordinator unavailable issue intermittently

by Anjith Paila (JIRA)

Anjith Paila created ISPN-7630: ---------------------------------- Summary: Getting coordinator unavailable issue intermittently Key: ISPN-7630 URL: https://issues.jboss.org/browse/ISPN-7630 Project: Infinispan Issue Type: Bug Components: Marshalling Affects Versions: 8.2.5.Final Reporter: Anjith Paila Priority: Minor Attachments: 0ksCZ.png We are using Inifinispan cluster with jgroups-tcp configuration in one of our setups. Sometimes we are observing that the coordinator status in jconsole is showing as unavailable, but this is not affecting any of the functionality. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7629) Administration console - fatal events have no icon in the right column latest events section

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7629?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7629: ------------------------------------ [~rmacor] Good spot! I forgot about the side bars :/ > Administration console - fatal events have no icon in the right column latest events section > -------------------------------------------------------------------------------------------- > > Key: ISPN-7629 > URL: https://issues.jboss.org/browse/ISPN-7629 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Ryan Emerson > Priority: Minor > > Fatal events such as "Lost data" event have no icon displayed in "Latest Grid Events" column on the right. > Note: > Status Events tab displays them correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7629) Administration console - fatal events have no icon in the right column latest events section

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7629?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7629: ------------------------------- Status: Open (was: New) > Administration console - fatal events have no icon in the right column latest events section > -------------------------------------------------------------------------------------------- > > Key: ISPN-7629 > URL: https://issues.jboss.org/browse/ISPN-7629 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Ryan Emerson > Priority: Minor > > Fatal events such as "Lost data" event have no icon displayed in "Latest Grid Events" column on the right. > Note: > Status Events tab displays them correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7629) Administration console - fatal events have no icon in the right column latest events section

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7629?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7629: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/198 > Administration console - fatal events have no icon in the right column latest events section > -------------------------------------------------------------------------------------------- > > Key: ISPN-7629 > URL: https://issues.jboss.org/browse/ISPN-7629 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Ryan Emerson > Priority: Minor > > Fatal events such as "Lost data" event have no icon displayed in "Latest Grid Events" column on the right. > Note: > Status Events tab displays them correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017