December 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8476) Add encryption support for Caching Service

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8476?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8476: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-container-images/jboss-dataservices-image/pull/57 > Add encryption support for Caching Service > ------------------------------------------ > > Key: ISPN-8476 > URL: https://issues.jboss.org/browse/ISPN-8476 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud > Reporter: Pedro Zapata > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8475) Add encryption support for Shared Memory

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8475?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8475: ------------------------------- Status: Open (was: New) > Add encryption support for Shared Memory > ---------------------------------------- > > Key: ISPN-8475 > URL: https://issues.jboss.org/browse/ISPN-8475 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud > Reporter: Pedro Zapata > Assignee: Ryan Emerson > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8475) Add encryption support for Shared Memory

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8475?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8475: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-container-images/jboss-dataservices-image/pull/57 > Add encryption support for Shared Memory > ---------------------------------------- > > Key: ISPN-8475 > URL: https://issues.jboss.org/browse/ISPN-8475 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud > Reporter: Pedro Zapata > Assignee: Ryan Emerson > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8618) Async Hot Rod client

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8618?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8618: ------------------------------ Component/s: Remote Protocols > Async Hot Rod client > -------------------- > > Key: ISPN-8618 > URL: https://issues.jboss.org/browse/ISPN-8618 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Radim Vansa > Assignee: Radim Vansa > > While we expose asynchronous operations in RemoteCache and more recently in counters and multimap, all communication is currently synchronous. > This is an umbrella task for handling communication asynchronously. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8620) Execute operations concurrently over the same connection

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8620?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8620: ------------------------------ Component/s: Remote Protocols > Execute operations concurrently over the same connection > -------------------------------------------------------- > > Key: ISPN-8620 > URL: https://issues.jboss.org/browse/ISPN-8620 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Protocols > Reporter: Radim Vansa > Assignee: Radim Vansa > > Since the early days Hot Rod protocol adds {{messageId}} to the protocol for pairing RPCs, but currently the connection is occupied when waiting for response. The goal of this is to reduce connection count and send the messages over shared connection. It requires some changes on server since it must continue reading the connection before the response is ready; the request needs to be processed asynchronously, too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8621) Share connection for events

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8621?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8621: ------------------------------ Component/s: Remote Protocols > Share connection for events > --------------------------- > > Key: ISPN-8621 > URL: https://issues.jboss.org/browse/ISPN-8621 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Protocols > Reporter: Radim Vansa > > Right now the event listeners require separate connection. With ISPN-8620 in place we can send the events along with responses and route them to listeners. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8619) Rewrite Hot Rod client using Netty

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8619?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8619: ------------------------------ Component/s: Remote Protocols > Rewrite Hot Rod client using Netty > ---------------------------------- > > Key: ISPN-8619 > URL: https://issues.jboss.org/browse/ISPN-8619 > Project: Infinispan > Issue Type: Sub-task > Components: Remote Protocols > Reporter: Radim Vansa > Assignee: Radim Vansa > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8530) Default value of "merge-policy" xsd attribute should not be a lambda

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8530?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8530. -------------------------------- Resolution: Done > Default value of "merge-policy" xsd attribute should not be a lambda > -------------------------------------------------------------------- > > Key: ISPN-8530 > URL: https://issues.jboss.org/browse/ISPN-8530 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final > Reporter: Adrian Nistor > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > > A different lambda name gets generated during each build. > So an xsd created and deployed to http://docs.jboss.org/infinispan/schemas/ becomes out of sync after next build. We can fix that by redeploying the schema but we cannot assume users will always re-fetch it. > Using static inner classes (non-anonymous) would be preferable in this case even though the lambda code looks nicer. This solution maintains backward compat with 9.1 too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8632) ConflictManager can cause deadlock on cache shutdown

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8632?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8632. -------------------------------- Resolution: Done > ConflictManager can cause deadlock on cache shutdown > ---------------------------------------------------- > > Key: ISPN-8632 > URL: https://issues.jboss.org/browse/ISPN-8632 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Beta2 > > > If stop is called on an EmbeddedCacheManager when the conflict resolution stage of a merge in ongoing, then it is impossible for ClusterCacheStatus::doLeave to proceed as ClusterCacheStatus::onPartitionMerge holds the ClusterCacheStatus lock. This is fine if conflict resolution completes successfully, however it is possible that the StateProviderImpl on the remote nodes has shutdown and therefore it's not possible for the ReplicaSpliterator to complete its execution and deadlock occurs. > To prevent the above scenario we should improve how the StateReceiverImpl and DefaultConflictManager handle stopping caches. Furthermore, we should also introduce a timeout when attempting to discover cache conflicts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8462) Enable custom EntryMergePolicy deployments on the server

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8462?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8462: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.Beta2 Resolution: Done > Enable custom EntryMergePolicy deployments on the server > -------------------------------------------------------- > > Key: ISPN-8462 > URL: https://issues.jboss.org/browse/ISPN-8462 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Beta2, 9.2.0.Final > > > It should be possible for users to deploy custom implementations of the EntryMergePolicy interface in the same manner that custom cache stores are deployed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2017