July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9135) Per-RemoteCache configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-9135?page=com.atlassian.jira.plugin... ] Tristan Tarrant resolved ISPN-9135. ----------------------------------- Fix Version/s: 11.0.0.Final Assignee: Tristan Tarrant Resolution: Duplicate Issue > Per-RemoteCache configuration > ----------------------------- > > Key: ISPN-9135 > URL: https://issues.redhat.com/browse/ISPN-9135 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 9.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > RemoteCaches do not have individual configuration as they inherit the RemoteCacheManager settings. This means that, in order to have different settings, multiple RemoteCacheManagers need to be instantiated. > In particular, the following settings should be per-cache: > * marshaller > * near cache > * forcereturnvalues -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7139) Consistent prefix in property names of Hot Rod client configurations

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-7139?page=com.atlassian.jira.plugin... ] Tristan Tarrant resolved ISPN-7139. ----------------------------------- Fix Version/s: 9.2.0.Final Resolution: Done > Consistent prefix in property names of Hot Rod client configurations > -------------------------------------------------------------------- > > Key: ISPN-7139 > URL: https://issues.redhat.com/browse/ISPN-7139 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Remote Protocols > Reporter: Sanne Grinovero > Priority: Major > Fix For: 9.2.0.Final > > > Most Hot Rod configuration properties use the prefix {{infinispan.client.hotrod.}} which makes it easy to recognize them. > Some properties don't use the prefix though, such as all those related to connection pooling, e.g. {{maxActive}}, {{maxTotal}}, .. > This makes it hard to read Hot Rod specific configuration properties from alternative sources. In particular we'd like to embed such properties in an Hibernate configuration file (for Hibernate OGM) but the fact that some properties need special handling forces us to keep a list of these to have special care, rather than being able to use a prefix like it is done in most such cases. > It should be easy to prefix all the properties, and deprecate the names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8668) Template configuration should be replicated across the cluster in standalone mode

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-8668?page=com.atlassian.jira.plugin... ] Tristan Tarrant closed ISPN-8668. --------------------------------- Resolution: Out of Date > Template configuration should be replicated across the cluster in standalone mode > --------------------------------------------------------------------------------- > > Key: ISPN-8668 > URL: https://issues.redhat.com/browse/ISPN-8668 > Project: Infinispan > Issue Type: Feature Request > Reporter: Diego Lovison > Priority: Minor > > Create a cluster with 3 servers in standalone mode. > You can create a cluster executing the following command: > ./standalone.sh -Djboss.socket.binding.port-offset=100 -Djboss.node.name=nodeA -c clustered.xml > ./standalone.sh -Djboss.socket.binding.port-offset=200 -Djboss.node.name=nodeB -c clustered.xml > ./standalone.sh -Djboss.socket.binding.port-offset=300 -Djboss.node.name=nodeC -c clustered.xml > Open the Web Console on the nodeA and create a template configuration. > The template configuration will not be replicated to nodeB and nodeC. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8341) CLI: Setting configuration cache attribute creates new cache-configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-8341?page=com.atlassian.jira.plugin... ] Tristan Tarrant closed ISPN-8341. --------------------------------- Resolution: Out of Date > CLI: Setting configuration cache attribute creates new cache-configuration > -------------------------------------------------------------------------- > > Key: ISPN-8341 > URL: https://issues.redhat.com/browse/ISPN-8341 > Project: Infinispan > Issue Type: Bug > Components: CLI, WildFly modules > Reporter: Sebastian Laskawiec > Assignee: Tristan Tarrant > Priority: Minor > > When I use the CLI to set cache template using the following command ({{cloud.xml}} configuration): > {code} > /subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=default:write-attribute(name=configuration, value=persistent-file-store-write-behind) > {code} > a new configuration element is added automatically. Here's how it looks like: > {code} > <cache-container name="clustered" default-cache="default" statistics="true"> > ... >  > <distributed-cache-configuration name="default"/> > </cache-container> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6619) New cache creation based on newly created configuration template over CLI requires server restart

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-6619?page=com.atlassian.jira.plugin... ] Tristan Tarrant closed ISPN-6619. --------------------------------- Resolution: Out of Date > New cache creation based on newly created configuration template over CLI requires server restart > ------------------------------------------------------------------------------------------------- > > Key: ISPN-6619 > URL: https://issues.redhat.com/browse/ISPN-6619 > Project: Infinispan > Issue Type: Bug > Components: CLI, Server > Reporter: Anna Manukyan > Priority: Major > > When adding new cache configuration template (with linked cache) or modifying the existing cache configuration template (e.g. enabling the compatibility mode or transaction) using CLI, then the cache configuration is not visible from the client. > The changes take affect only after the server restart. > I would expect the cache be accessible right after the CLI changes are done. > You can find the steps for reproduction in according section. > Note: if only cache is created using CLI based on the existing configuration template (which was available before server start), then everything works fine - the configuration is applied to the newly created cache. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7818) Provide an unauthenticated server configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-7818?page=com.atlassian.jira.plugin... ] Tristan Tarrant closed ISPN-7818. --------------------------------- Resolution: Out of Date > Provide an unauthenticated server configuration > ----------------------------------------------- > > Key: ISPN-7818 > URL: https://issues.redhat.com/browse/ISPN-7818 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Katia Aresti > Priority: Major > > While authenticated should be on by default in server, users should have a quick way to use server in unauthenticated way for performance reasons...etc. So, provide a unauthenticated configuration in the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12083) Filter counters

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12083?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12083: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Filter counters > ---------------- > > Key: ISPN-12083 > URL: https://issues.redhat.com/browse/ISPN-12083 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Filter counters into weak and strong context selector and display the config depending on the counter type -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12084) Delete counter

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12084?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12084: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Delete counter > -------------- > > Key: ISPN-12084 > URL: https://issues.redhat.com/browse/ISPN-12084 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > [https://marvelapp.com/8d66729/screen/69367860] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12103) Improve ContainerDatabase to add custom wait strategy

by Gustavo Lira e Silva (Jira)

Gustavo Lira e Silva created ISPN-12103: ------------------------------------------- Summary: Improve ContainerDatabase to add custom wait strategy Key: ISPN-12103 URL: https://issues.redhat.com/browse/ISPN-12103 Project: Infinispan Issue Type: Enhancement Components: Test Suite Affects Versions: 11.0.1.Final Reporter: Gustavo Lira e Silva Assignee: Gustavo Lira e Silva Some databases needs extra container privilege and also needs a custom {{waitstrategy}} instead of just use the default {{Wait.forListeningPort()}}, for example DB2 needs an extra time after the ListeningPorts be available to create the datasource and finish the setup. The idea is to implement a {{LogMessageWaitStrategy}} with a regex expression to identify when the container is ready indeed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11336) Infinispan BOM should only have dependency management

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11336?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11336: ------------------------------- Sprint: DataGrid Sprint #46 > Infinispan BOM should only have dependency management > ----------------------------------------------------- > > Key: ISPN-11336 > URL: https://issues.redhat.com/browse/ISPN-11336 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.2.Final > Reporter: Stéphane Nicoll > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > The BOM has a {{pluginManagement}} section that's a bit misleading since Maven isn't going to do anything with it. > It is also invalid at the moment per the following: > {code:xml} > <plugin> > <groupId>org.infinispan.maven-plugins</groupId> > <artifactId>protocol-parser-generator</artifactId> > <version>${version.infinispan.maven-plugins}</version> > </plugin> > {code} > This artifact does not seem to be published anymore. Using the BOM with resolution leads to > {noformat} > [WARNING] The POM for org.infinispan:infinispan-protocol-parser-generator-maven-plugin:jar:10.1.1.Final is missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for org.infinispan:infinispan-protocol-parser-generator-maven-plugin:10.1.1.Final: Plugin org.infinispan:infinispan-protocol-parser-generator-maven-plugin:10.1.1.Final or one of its dependencies could not be resolved: Failure to find org.infinispan:infinispan-protocol-parser-generator-maven-plugin:jar:10.1.1.Final in https://repo.spring.io/milestone was cached in the local repository, resolution will not be reattempted until the update interval of spring-milestones has elapsed or updates are forced > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2020