February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-6724) Modules scripting and infinispan directory provider use the same logging id range

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6724?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6724: ---------------------------------- Fix Version/s: (was: 9.0.0.CR3) > Modules scripting and infinispan directory provider use the same logging id range > --------------------------------------------------------------------------------- > > Key: ISPN-6724 > URL: https://issues.jboss.org/browse/ISPN-6724 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6724) Modules scripting and infinispan directory provider use the same logging id range

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6724?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6724: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4909 > Modules scripting and infinispan directory provider use the same logging id range > --------------------------------------------------------------------------------- > > Key: ISPN-6724 > URL: https://issues.jboss.org/browse/ISPN-6724 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6724) Modules scripting and infinispan directory provider use the same logging id range

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6724?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6724: ------------------------------------- Assignee: Tristan Tarrant > Modules scripting and infinispan directory provider use the same logging id range > --------------------------------------------------------------------------------- > > Key: ISPN-6724 > URL: https://issues.jboss.org/browse/ISPN-6724 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 9.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5187) Node.js HotRod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5187?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5187: ---------------------------------- Fix Version/s: 8.2.0.Final (was: 9.0.0.Final) > Node.js HotRod client > --------------------- > > Key: ISPN-5187 > URL: https://issues.jboss.org/browse/ISPN-5187 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Fix For: 8.2.0.Final > > > Either implement a pure javascript client or base on the native C++ client. Should be L2/L3 aware. > Initial scope: > * L1, L2, L3 > * Async API (no sync API) > * Remote queries > * Remote Task execution > Target for 8.2+ > * Remote events / listeners > * Cross site failover > * Security > * Encryption TLS > * Authentication SASL -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5187) Node.js HotRod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5187?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-5187. --------------------------------- Resolution: Done > Node.js HotRod client > --------------------- > > Key: ISPN-5187 > URL: https://issues.jboss.org/browse/ISPN-5187 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Fix For: 8.2.0.Final > > > Either implement a pure javascript client or base on the native C++ client. Should be L2/L3 aware. > Initial scope: > * L1, L2, L3 > * Async API (no sync API) > * Remote queries > * Remote Task execution > Target for 8.2+ > * Remote events / listeners > * Cross site failover > * Security > * Encryption TLS > * Authentication SASL -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5721) Add SNI support to the endpoints

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5721?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-5721. ----------------------------------- Resolution: Done > Add SNI support to the endpoints > -------------------------------- > > Key: ISPN-5721 > URL: https://issues.jboss.org/browse/ISPN-5721 > Project: Infinispan > Issue Type: Feature Request > Components: Security, Server > Affects Versions: 8.0.0.Final > Reporter: Tristan Tarrant > Assignee: Sebastian Łaskawiec > Fix For: 9.0.0.Final, 9.0.0.Alpha2 > > > Openshift Router uses DNS names to perform routing. It is perfectly legal to have this kind of configuration: > {code} > client 1 --> example.com:11222 -----+> Hotrod server > / > client 2 --> example2.com:11222 / > {code} > In that case the TLS configuration might be problematic (since very often certificates are issued for a domain name). However it is possible to use [SNI TLS Extension|https://tools.ietf.org/html/rfc6066#page-6]. > The SNI needs to be added to: > * Client's configuration (it needs to modify it's own {{SSLContext}} and add {{SSLParams}} > * Hotrod server to support SNI (with Netty) > * XML Configuration for Hotrod -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6267) Create a deployable infinispan subsystem for WildFly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6267?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-6267. --------------------------------- Resolution: Duplicate Issue > Create a deployable infinispan subsystem for WildFly > ---------------------------------------------------- > > Key: ISPN-6267 > URL: https://issues.jboss.org/browse/ISPN-6267 > Project: Infinispan > Issue Type: Feature Request > Components: WildFly modules > Reporter: Tristan Tarrant > Fix For: 9.1.0.Final > > > We should extrapolate our server Infinispan subsystem and package it together with the WildFly modules so that caches can be created at the server level. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6060) Add aggregation and grouping to continuous query

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6060?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6060: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) > Add aggregation and grouping to continuous query > ------------------------------------------------ > > Key: ISPN-6060 > URL: https://issues.jboss.org/browse/ISPN-6060 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > To be defined. > This only makes sense for the materialized view approach of continuous query, which is not implemented yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6267) Create a deployable infinispan subsystem for WildFly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6267?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6267: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > Create a deployable infinispan subsystem for WildFly > ---------------------------------------------------- > > Key: ISPN-6267 > URL: https://issues.jboss.org/browse/ISPN-6267 > Project: Infinispan > Issue Type: Feature Request > Components: WildFly modules > Reporter: Tristan Tarrant > Fix For: 9.1.0.Final > > > We should extrapolate our server Infinispan subsystem and package it together with the WildFly modules so that caches can be created at the server level. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7470) Distributed executor does not fail over unless future.get() is called

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7470?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7470: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) > Distributed executor does not fail over unless future.get() is called > --------------------------------------------------------------------- > > Key: ISPN-7470 > URL: https://issues.jboss.org/browse/ISPN-7470 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR1, 8.2.6.Final > Reporter: Dan Berindei > Assignee: William Burns > > After ISPN-6392, {{DistributedExecutorService.submit(...)}} nominally returns a {{CompletableFuture}}. However, it doesn't behave like a regular {{CompletableFuture}}, because it doesn't run the failure policy until the user calls {{future.get()}}. > {{future.isComplete()}} will return {{true}} before running the failure policy, and {{future.whenComplete(callback)}} will also execute the callback before running the failure policy. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017