December 2020 - infinispan-issues

[Red Hat JIRA] (ISPN-12561) CacheV2ResourceTest does not close RestClient responses

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12561?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12561: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > CacheV2ResourceTest does not close RestClient responses > ------------------------------------------------------- > > Key: ISPN-12561 > URL: https://issues.redhat.com/browse/ISPN-12561 > Project: Infinispan > Issue Type: Bug > Components: REST, Test Suite > Affects Versions: 12.0.0.Dev07 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 12.0.0.CR1 > > > {{RestClient}} needs responses with bodies to be closed, either explicitly, or implicitly by reading the entire body. {{CacheV2ResourceTest}} checks only the HTTP status for most responses, without reading the body. > OkHttpClient logs a WARN message when a response is not closed. If debug logging is enabled for {{okhttp3.OkHttpClient}}, the message includes a stack trace: > {noformat} > 10:22:36,569 WARN (OkHttp ConnectionPool) [OkHttpClient] A connection to https://localhost:43483/ was leaked. Did you forget to close a response body? > java.lang.Throwable: response.body().close() > at okhttp3.internal.platform.Platform.getStackTraceForCloseable(Platform.java:149) > at okhttp3.internal.connection.Transmitter.callStart(Transmitter.java:116) > at okhttp3.RealCall.enqueue(RealCall.java:92) > at org.infinispan.client.rest.impl.okhttp.RestClientOkHttp.execute(RestClientOkHttp.java:248) > at org.infinispan.client.rest.impl.okhttp.RestCacheClientOkHttp.post(RestCacheClientOkHttp.java:94) > at org.infinispan.rest.resources.CacheV2ResourceTest.testCacheV2KeyOps(CacheV2ResourceTest.java:142) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12582) CLI aliases are not persistent

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12582?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12582: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8939 > CLI aliases are not persistent > ------------------------------ > > Key: ISPN-12582 > URL: https://issues.redhat.com/browse/ISPN-12582 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Priority: Major > > alias command in CLI is to set shortcuts > like > alias co=connect > so far it works, but I assume that it should be stored in .config/infinispan/aliases which not happen > also set something in aliases files and start CLI will not work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12582) CLI aliases are not persistent

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12582?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12582: ----------------------------------- Fix Version/s: 12.0.0.CR1 > CLI aliases are not persistent > ------------------------------ > > Key: ISPN-12582 > URL: https://issues.redhat.com/browse/ISPN-12582 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.CR1 > > > alias command in CLI is to set shortcuts > like > alias co=connect > so far it works, but I assume that it should be stored in .config/infinispan/aliases which not happen > also set something in aliases files and start CLI will not work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12582) CLI aliases are not persistent

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12582?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12582: ----------------------------------- Status: Open (was: New) > CLI aliases are not persistent > ------------------------------ > > Key: ISPN-12582 > URL: https://issues.redhat.com/browse/ISPN-12582 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Priority: Major > > alias command in CLI is to set shortcuts > like > alias co=connect > so far it works, but I assume that it should be stored in .config/infinispan/aliases which not happen > also set something in aliases files and start CLI will not work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12582) CLI aliases are not persistent

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12582?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-12582: -------------------------------------- Assignee: Tristan Tarrant > CLI aliases are not persistent > ------------------------------ > > Key: ISPN-12582 > URL: https://issues.redhat.com/browse/ISPN-12582 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Priority: Major > > alias command in CLI is to set shortcuts > like > alias co=connect > so far it works, but I assume that it should be stored in .config/infinispan/aliases which not happen > also set something in aliases files and start CLI will not work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12582) CLI aliases are not persistent

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12582?page=com.atlassian.jira.plugi... ] Tristan Tarrant commented on ISPN-12582: ---------------------------------------- Aesh has a bug where it fails to load persisted aliases and resets them on startup > CLI aliases are not persistent > ------------------------------ > > Key: ISPN-12582 > URL: https://issues.redhat.com/browse/ISPN-12582 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Priority: Major > > alias command in CLI is to set shortcuts > like > alias co=connect > so far it works, but I assume that it should be stored in .config/infinispan/aliases which not happen > also set something in aliases files and start CLI will not work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12582) CLI aliases are not persistent

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12582: --------------------------------------- Summary: CLI aliases are not persistent Key: ISPN-12582 URL: https://issues.redhat.com/browse/ISPN-12582 Project: Infinispan Issue Type: Bug Reporter: Wolf-Dieter Fink alias command in CLI is to set shortcuts like alias co=connect so far it works, but I assume that it should be stored in .config/infinispan/aliases which not happen also set something in aliases files and start CLI will not work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12261) Protocol server transport management

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12261?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12261: ----------------------------------- Description: the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240). The new server should have a similar capability. h4. Protocol management via CLI {noformat} $ cli.sh server connector ls $ cli.sh server connector describe endpoint-default $ cli.sh server connector stop endpoint-default $ cli.sh server connector start endpoint-default {noformat} Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively. h4. IP Filtering {code:xml} <endpoints socket-binding="default" security-realm="default"> <ip-filter> <reject from="172.16.0.0/16"/> <accept from="127.0.0.0/8"/> </ip-filter> <hotrod-connector/> <rest-connector/> </endpoints> {code} was: the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240). The new server should have a similar capability. h4. Protocol management via CLI {noformat} $ cli.sh connector status $ cli.sh connector stop hotrod $ cli.sh connector start hotrod {noformat} Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively. h4. IP Filtering {code:xml} <endpoints socket-binding="default" security-realm="default"> <ip-filter> <reject from="172.16.0.0/16"/> <accept from="127.0.0.0/8"/> </ip-filter> <hotrod-connector/> <rest-connector/> </endpoints> {code} > Protocol server transport management > ------------------------------------- > > Key: ISPN-12261 > URL: https://issues.redhat.com/browse/ISPN-12261 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, JMX, reporting and management, Server > Affects Versions: 12.0.0.Dev02 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.CR1 > > > the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240). > The new server should have a similar capability. > h4. Protocol management via CLI > {noformat} > $ cli.sh server connector ls > $ cli.sh server connector describe endpoint-default > $ cli.sh server connector stop endpoint-default > $ cli.sh server connector start endpoint-default > {noformat} > Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively. > h4. IP Filtering > {code:xml} > <endpoints socket-binding="default" security-realm="default"> > <ip-filter> > <reject from="172.16.0.0/16"/> > <accept from="127.0.0.0/8"/> > </ip-filter> > <hotrod-connector/> > <rest-connector/> > </endpoints> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12581) Filter authentication mechanism on the Elytron authenticator

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-12581: -------------------------------------- Summary: Filter authentication mechanism on the Elytron authenticator Key: ISPN-12581 URL: https://issues.redhat.com/browse/ISPN-12581 Project: Infinispan Issue Type: Bug Components: Security, Server Affects Versions: 12.0.0.Dev07, 11.0.8.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 12.0.0.CR1, 11.0.9.Final The ElytronHTTPAuthenticator and ElytronSASLAuthenticationProvider should use a FilterMechanism* factory to only allow configured mechs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12579) Able to choose operator version documentation at the site

by Dmitry Volodin (Jira)

[ https://issues.redhat.com/browse/ISPN-12579?page=com.atlassian.jira.plugi... ] Dmitry Volodin updated ISPN-12579: ---------------------------------- Description: Number of Infinispan operator release become countable. It would be nice to choose version at the site documentation Also mapping between operator version and Infinispan server version would be prefer to publish in the documentation > Able to choose operator version documentation at the site > --------------------------------------------------------- > > Key: ISPN-12579 > URL: https://issues.redhat.com/browse/ISPN-12579 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation, Operator, Website > Reporter: Dmitry Volodin > Assignee: Donald Naro > Priority: Minor > > Number of Infinispan operator release become countable. It would be nice to choose version at the site documentation > Also mapping between operator version and Infinispan server version would be prefer to publish in the documentation -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 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 December 2020