October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10699) Add Transcoder name to log statements to aid debugging

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10699?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10699: -------------------------------- Status: Open (was: New) > Add Transcoder name to log statements to aid debugging > ------------------------------------------------------ > > Key: ISPN-10699 > URL: https://issues.jboss.org/browse/ISPN-10699 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.0.0.CR2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR3 > > > Currently the error message returned to the client when a transcoding exception occurs is not very detailed as the stack trace is where the `HotRodClientException` is thrown and the server error message does not detail the transcoder that encountered the issue. > We should include the name of the transcoder in the server exception to aid debugging. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10699) Add Transcoder name to log statements to aid debugging

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10699: ----------------------------------- Summary: Add Transcoder name to log statements to aid debugging Key: ISPN-10699 URL: https://issues.jboss.org/browse/ISPN-10699 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 10.0.0.CR2 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.CR3 Currently the error message returned to the client when a transcoding exception occurs is not very detailed as the stack trace is where the `HotRodClientException` is thrown and the server error message does not detail the transcoder that encountered the issue. We should include the name of the transcoder in the server exception to aid debugging. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10609) Extend Marshaller interface to expose configured ClassWhiteList to implementation

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10609?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10609: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7302 > Extend Marshaller interface to expose configured ClassWhiteList to implementation > --------------------------------------------------------------------------------- > > Key: ISPN-10609 > URL: https://issues.jboss.org/browse/ISPN-10609 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.0.0.CR2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR3 > > > ClassWhiteList is a generic white list that can be configured via our XML, it doesn't have anything specifc to Serialization. We should allow a user's marshaller implementation, set via SerializationConfiguration#marshaller, to utilise the configured values to limit what can/can't be marshalled. > For our internal code this is nice because it will prevent us from requiring hacky code like the following in the PersistenceMarshallerImpl if the user wants to utilise our provided JavaSerializationMarshaller: > {code:java} > if (userMarshaller instanceof JavaSerializationMarshaller) { > ((JavaSerialzationMarshaller) userMarshaller).setWhiteList(whiteListImpl); > } else if (userMarshaller instanceof ...) { > ... > } > {code} > Proposed change to the Marshaller interface: > {code:java} > default void initialize(ClassWhiteList whiteList) { > // no-op > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10609) Extend Marshaller interface to expose configured ClassWhiteList to implementation

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10609?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10609: -------------------------------- Status: Open (was: New) > Extend Marshaller interface to expose configured ClassWhiteList to implementation > --------------------------------------------------------------------------------- > > Key: ISPN-10609 > URL: https://issues.jboss.org/browse/ISPN-10609 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.0.0.CR2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR3 > > > ClassWhiteList is a generic white list that can be configured via our XML, it doesn't have anything specifc to Serialization. We should allow a user's marshaller implementation, set via SerializationConfiguration#marshaller, to utilise the configured values to limit what can/can't be marshalled. > For our internal code this is nice because it will prevent us from requiring hacky code like the following in the PersistenceMarshallerImpl if the user wants to utilise our provided JavaSerializationMarshaller: > {code:java} > if (userMarshaller instanceof JavaSerializationMarshaller) { > ((JavaSerialzationMarshaller) userMarshaller).setWhiteList(whiteListImpl); > } else if (userMarshaller instanceof ...) { > ... > } > {code} > Proposed change to the Marshaller interface: > {code:java} > default void initialize(ClassWhiteList whiteList) { > // no-op > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10693) Docs: Update anchors and links

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10693?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10693. --------------------------------- Fix Version/s: 10.0.0.CR3 Resolution: Done > Docs: Update anchors and links > ------------------------------ > > Key: ISPN-10693 > URL: https://issues.jboss.org/browse/ISPN-10693 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.0.0.CR3 > > > Make sure all anchors and links are correct for community. No pointers to the user guide. > Also from https://github.com/infinispan/infinispan/pull/7367 - change store_binary anchor to store_as_binary -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9950) ServerNG: CLI

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9950?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9950: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7304 > ServerNG: CLI > ------------- > > Key: ISPN-9950 > URL: https://issues.jboss.org/browse/ISPN-9950 > Project: Infinispan > Issue Type: Sub-task > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9950) ServerNG: CLI

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9950?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9950: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR3 Resolution: Done > ServerNG: CLI > ------------- > > Key: ISPN-9950 > URL: https://issues.jboss.org/browse/ISPN-9950 > Project: Infinispan > Issue Type: Sub-task > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10685) File stores locations do not respect the Global State persistent location

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10685?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10685: -------------------------------- Status: Pull Request Sent (was: Reopened) > File stores locations do not respect the Global State persistent location > -------------------------------------------------------------------------- > > Key: ISPN-10685 > URL: https://issues.jboss.org/browse/ISPN-10685 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > The file stores (Single, SoftIndex, RocksDB) should create files relative to the GlobalState persistent location unless specified. > Additionally each of the file stores differs in the filesystem layout: > * The SoftIndex store does not use the name of the cache in the file path, preventing sharing of directories between multiple caches. > * The RocksDB store allows configuring data and expired locations to point to the same directory, which will result in data corruption -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10685) File stores locations do not respect the Global State persistent location

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10685?page=com.atlassian.jira.plugin... ] Ryan Emerson reopened ISPN-10685: --------------------------------- > File stores locations do not respect the Global State persistent location > -------------------------------------------------------------------------- > > Key: ISPN-10685 > URL: https://issues.jboss.org/browse/ISPN-10685 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > The file stores (Single, SoftIndex, RocksDB) should create files relative to the GlobalState persistent location unless specified. > Additionally each of the file stores differs in the filesystem layout: > * The SoftIndex store does not use the name of the cache in the file path, preventing sharing of directories between multiple caches. > * The RocksDB store allows configuring data and expired locations to point to the same directory, which will result in data corruption -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10685) File stores locations do not respect the Global State persistent location

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10685?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10685: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7365, https://github.com/infinispan/infinispan/pull/7380 (was: https://github.com/infinispan/infinispan/pull/7365) > File stores locations do not respect the Global State persistent location > -------------------------------------------------------------------------- > > Key: ISPN-10685 > URL: https://issues.jboss.org/browse/ISPN-10685 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > The file stores (Single, SoftIndex, RocksDB) should create files relative to the GlobalState persistent location unless specified. > Additionally each of the file stores differs in the filesystem layout: > * The SoftIndex store does not use the name of the cache in the file path, preventing sharing of directories between multiple caches. > * The RocksDB store allows configuring data and expired locations to point to the same directory, which will result in data corruption -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2019