June 2020 - infinispan-issues - Jboss List Archives

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

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11980?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11980: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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-11980) Storage type HEAP default encoding should be application/x-java-object

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11980?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11980: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8463 > 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-11782) Docs: Cross-Site monitoring

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11782?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11782: ------------------------------- Sprint: (was: DataGrid Sprint #45) > Docs: Cross-Site monitoring > --------------------------- > > Key: ISPN-11782 > URL: https://issues.redhat.com/browse/ISPN-11782 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Add details about monitoring cross-site operations like state transfer etc. -- 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 Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11980?page=com.atlassian.jira.plugi... ] Gustavo Fernandes edited comment on ISPN-11980 at 6/11/20 2:26 PM: ------------------------------------------------------------------- The issue is actually using {{storageType(HEAP)}} {{storageType()}} is deprecated and {{HEAP}} is a replacement for {{OBJECT}} was (Author: gustavonalle): The issue is actually using storageType(HEAP): storageType() is deprecated and HEAP is a replacement for OBJECT > 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-11980) Storage type HEAP default encoding should be application/x-java-object

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11980?page=com.atlassian.jira.plugi... ] Gustavo Fernandes commented on ISPN-11980: ------------------------------------------ The issue is actually using storageType(HEAP): storageType() is deprecated and HEAP is a replacement for OBJECT > 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-11868) Docs: Update Spring Session for defining caches

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11868?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11868: ------------------------------- Sprint: (was: DataGrid Sprint #45) > Docs: Update Spring Session for defining caches > ----------------------------------------------- > > Key: ISPN-11868 > URL: https://issues.redhat.com/browse/ISPN-11868 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > https://infinispan.zulipchat.com/#narrow/stream/118645-infinispan/topic/d... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11759) ProtocolServer should use BlockingManager instead of Executor

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11759?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11759: ------------------------------ Status: Open (was: Pull Request Sent) > ProtocolServer should use BlockingManager instead of Executor > ------------------------------------------------------------- > > Key: ISPN-11759 > URL: https://issues.redhat.com/browse/ISPN-11759 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > Protocol Servers use an Executor to submit tasks that may block. We should instead use the new BlockingManager as it properly handles the blocking threads. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11784) Combine netty and non blocking thread pools

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11784?page=com.atlassian.jira.plugi... ] Work on ISPN-11784 stopped by Will Burns. ----------------------------------------- > Combine netty and non blocking thread pools > ------------------------------------------- > > Key: ISPN-11784 > URL: https://issues.redhat.com/browse/ISPN-11784 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We cannot simply drop in our non blocking thread pool as an executor for netty io event loop group. The reason is because Netty takes over control of that thread and only runs tasks submitted to its various event loops. To consolidate these we need to replace our non blocking thread pool with the netty thread pool so it can awake the thread to process tasks. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11869) Docs: Update for deprecated memory configuration

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11869?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11869: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Final Resolution: Done > Docs: Update for deprecated memory configuration > ------------------------------------------------ > > Key: ISPN-11869 > URL: https://issues.redhat.com/browse/ISPN-11869 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > Fix For: 11.0.0.Final > > > https://infinispan.org/docs/dev/titles/configuring/configuring.html#memory is completely changed with 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11994) RemoteCacheImpl.retrieveEntries with explicit segments is not server aware

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11994: ---------------------------------------- Summary: RemoteCacheImpl.retrieveEntries with explicit segments is not server aware Key: ISPN-11994 URL: https://issues.redhat.com/browse/ISPN-11994 Project: Infinispan Issue Type: Bug Components: Hot Rod Reporter: Will Burns Assignee: Will Burns Unfortunately retrieveEntries method always chooses a random server to send a request to. This is fine when segments is not provided. However if an explicit set of segments is provided we should route the request to the address that has the most segments of the set and hasn't failed yet. -- 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