June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11974: -------------------------------- Status: Open (was: New) > Remove GenericJbossMarshaller automatic configuration > ----------------------------------------------------- > > Key: ISPN-11974 > URL: https://issues.redhat.com/browse/ISPN-11974 > Project: Infinispan > Issue Type: Task > Components: Configuration, Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should no automatically configure this marshaller if the module is present. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11959) Add custom NonBlockingStore server test

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11959?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11959: ------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8428, https://github.com/infinispan/infinispan/pull/8443 (was: https://github.com/infinispan/infinispan/pull/8428) > Add custom NonBlockingStore server test > --------------------------------------- > > Key: ISPN-11959 > URL: https://issues.redhat.com/browse/ISPN-11959 > Project: Infinispan > Issue Type: Task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We have the new SPI with ISPN-10373. We should add a test that verifies this works in the infinispan-server-tests module. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11981) Stale immortal entry metadata

by Dan Berindei (Jira)

Dan Berindei created ISPN-11981: ----------------------------------- Summary: Stale immortal entry metadata Key: ISPN-11981 URL: https://issues.redhat.com/browse/ISPN-11981 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.1.8.Final, 11.0.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.0.Final When an entry is updated, {{InternalEntryFactoryImpl}} tries to reuse the existing {{InternalCacheEntry}} instance instead of creating a new one. The condition is that both the new and the old entry have the same implementation implementation: immortal, immortal w/ external metadata, transient, transient w/ metadata etc. Because {{MetadataImmortalCacheEntry}} extends {{ImmortalCacheEntry}}, that logic is broken: when an immortal entry with external metadata is replaced with a new entry without external metadata, the external metadata is not removed. This impacts the anchored keys module, which I am changing to store the key location in the metadata (currently it is stored as a value, and it is broken with BINARY/OFF_HEAP storage). When a node leaves and an entry located on the leaver is updated, the key is written on the newest joiner. The joiner already has a local entry with {{RemoteMetadata}}, and is trying to write a value without any metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11981) Stale immortal entry metadata

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11981?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11981: -------------------------------- Status: Open (was: New) > Stale immortal entry metadata > ----------------------------- > > Key: ISPN-11981 > URL: https://issues.redhat.com/browse/ISPN-11981 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.0.CR1, 10.1.8.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > When an entry is updated, {{InternalEntryFactoryImpl}} tries to reuse the existing {{InternalCacheEntry}} instance instead of creating a new one. The condition is that both the new and the old entry have the same implementation implementation: immortal, immortal w/ external metadata, transient, transient w/ metadata etc. > Because {{MetadataImmortalCacheEntry}} extends {{ImmortalCacheEntry}}, that logic is broken: when an immortal entry with external metadata is replaced with a new entry without external metadata, the external metadata is not removed. > This impacts the anchored keys module, which I am changing to store the key location in the metadata (currently it is stored as a value, and it is broken with BINARY/OFF_HEAP storage). When a node leaves and an entry located on the leaver is updated, the key is written on the newest joiner. The joiner already has a local entry with {{RemoteMetadata}}, and is trying to write a value without any metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11980) Storage type HEAP default encoding should be application/x-java-object

by Dan Berindei (Jira)

Dan Berindei created ISPN-11980: ----------------------------------- Summary: Storage type HEAP default encoding should be application/x-java-object Key: ISPN-11980 URL: https://issues.redhat.com/browse/ISPN-11980 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 11.0.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.0.Final Storage type {{HEAP}} is supposed to be a replacement for {{OBJECT+BINARY}}, storing POJOs in the data container by default but allowing the user to store serialized keys and values by configuring an encoding other than {{application/x-java-object}}. The current {{StorageConfigurationManager}} code doesn't work like that, and the default encoding for {{HEAP}} storage is the user marshaller's media type (by default {{application/x-protostream}}). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11980) Storage type HEAP default encoding should be application/x-java-object

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11980?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11980: -------------------------------- Status: Open (was: New) > Storage type HEAP default encoding should be application/x-java-object > ---------------------------------------------------------------------- > > Key: ISPN-11980 > URL: https://issues.redhat.com/browse/ISPN-11980 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > Storage type {{HEAP}} is supposed to be a replacement for {{OBJECT+BINARY}}, storing POJOs in the data container by default but allowing the user to store serialized keys and values by configuring an encoding other than {{application/x-java-object}}. > The current {{StorageConfigurationManager}} code doesn't work like that, and the default encoding for {{HEAP}} storage is the user marshaller's media type (by default {{application/x-protostream}}). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11971) Add a JVM property to enable all CORS permissions

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11971?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11971: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add a JVM property to enable all CORS permissions > ------------------------------------------------- > > Key: ISPN-11971 > URL: https://issues.redhat.com/browse/ISPN-11971 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7646) AtomicMap doesn't work with StorageType.BINARY/OFF_HEAP

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-7646?page=com.atlassian.jira.plugin... ] Dan Berindei closed ISPN-7646. ------------------------------ Resolution: Out of Date {{AtomicMap}} was reduced in 10.0 with ISPN-10230 > AtomicMap doesn't work with StorageType.BINARY/OFF_HEAP > ------------------------------------------------------- > > Key: ISPN-7646 > URL: https://issues.redhat.com/browse/ISPN-7646 > Project: Infinispan > Issue Type: Feature Request > Reporter: Seto Kaiba > Priority: Major > > AtomicMap doesn't work with StorageType.BINARY/OFF_HEAP -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11925) Docs: Updates for deprecated thread pool config and non-blocking persistence SPI

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11925?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11925: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Final Resolution: Done > Docs: Updates for deprecated thread pool config and non-blocking persistence SPI > -------------------------------------------------------------------------------- > > Key: ISPN-11925 > URL: https://issues.redhat.com/browse/ISPN-11925 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > Fix For: 11.0.0.Final > > > org.infinispan.configuration.cache.AsyncStoreConfiguration#threadPoolSize() is deprecated along with several other thread pool config bits. need to update examples in docs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11979) REST resources for server need to wrap privileged actions

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11979?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11979: ------------------------------------- Status: Open (was: New) > REST resources for server need to wrap privileged actions > --------------------------------------------------------- > > Key: ISPN-11979 > URL: https://issues.redhat.com/browse/ISPN-11979 > Project: Infinispan > Issue Type: Enhancement > Components: REST, Server > Reporter: Gustavo Fernandes > Priority: Major > > ClusterResource, LoginResource, ServerResource and LoggingResource should have all privileged actions wrapped in SecurityActions -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 June 2020