July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12094) Default JGroups configuration files result in WARN log messages

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-12094?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-12094: -------------------------------- Priority: Major (was: Critical) > Default JGroups configuration files result in WARN log messages > --------------------------------------------------------------- > > Key: ISPN-12094 > URL: https://issues.redhat.com/browse/ISPN-12094 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.8.Final, 11.0.1.Final > Reporter: Paul Ferraro > Priority: Major > > The default JGroups configuration files found here: > [https://github.com/infinispan/infinispan/tree/10.1.x/core/src/main/resour...] > generate the following log message when parsed: > {noformat} > 2020-07-07 08:55:30,087 WARN [org.jgroups.conf.XmlConfigurator] (ServerService Thread Pool -- 84) version is missing in the configuration file{noformat} > > This is due to logic added to JGroups since this commit: > [https://github.com/belaban/JGroups/commit/254ea2d10029afbd92428f7857041a1...] > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12094) Default JGroups configuration files result in WARN log messages

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-12094?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-12094: -------------------------------- Description: The default JGroups configuration files found here: [https://github.com/infinispan/infinispan/tree/10.1.x/core/src/main/resour...] generate the following log message when parsed: {noformat} 2020-07-07 08:55:30,087 WARN [org.jgroups.conf.XmlConfigurator] (ServerService Thread Pool -- 84) version is missing in the configuration file{noformat} This is due to logic added to JGroups since this commit: [https://github.com/belaban/JGroups/commit/254ea2d10029afbd92428f7857041a1...] was: The default JGroups configuration files found here: [https://github.com/infinispan/infinispan/tree/10.1.x/core/src/main/resour...] generate the following log message when parsed: {noformat} 2020-07-07 08:55:30,087 WARN [org.jgroups.conf.XmlConfigurator] (ServerService Thread Pool -- 84) version is missing in the configuration file{noformat} This is due to logic added to JGroups since this commit: [https://github.com/belaban/JGroups/commit/254ea2d10029afbd92428f7857041a1...] While this is just log noise, it has the unfortunate priority due to the linked issue. > Default JGroups configuration files result in WARN log messages > --------------------------------------------------------------- > > Key: ISPN-12094 > URL: https://issues.redhat.com/browse/ISPN-12094 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.8.Final, 11.0.1.Final > Reporter: Paul Ferraro > Priority: Critical > > The default JGroups configuration files found here: > [https://github.com/infinispan/infinispan/tree/10.1.x/core/src/main/resour...] > generate the following log message when parsed: > {noformat} > 2020-07-07 08:55:30,087 WARN [org.jgroups.conf.XmlConfigurator] (ServerService Thread Pool -- 84) version is missing in the configuration file{noformat} > > This is due to logic added to JGroups since this commit: > [https://github.com/belaban/JGroups/commit/254ea2d10029afbd92428f7857041a1...] > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

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

by Stéphane Nicoll (Jira)

[ https://issues.redhat.com/browse/ISPN-11336?page=com.atlassian.jira.plugi... ] Stéphane Nicoll commented on ISPN-11336: ---------------------------------------- This issue prevents the Spring Boot project to use the BOM for its dependency management. As we have to copy over all modules, fixing this issue would help us be consistent with what this project wants to promote. > 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 > Priority: Major > > 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)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11802: ------------------------------- Fix Version/s: 12.0.0.Dev01 > Create SPI for Cross-Site Replication conflict resolution > --------------------------------------------------------- > > Key: ISPN-11802 > URL: https://issues.redhat.com/browse/ISPN-11802 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > A conflict happens if 2 sites try to update the same key (put/remove) concurrently. > With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update. > h2. Interface > {code:java} > interface ABC<V> { // or concrete class > String site(); //the site name which wrote this value > V value(); // the value. can be null if the key was removed > Metadata metadata(); //can be null > } > interface Resolve<K, V> { > ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2); > } > {code} > h2. Configuration > Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name. > For server mode, you need to add your jar with the classes required to {{server/lib}}. > The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy. > {code:java} > ConfigurationBuilder.sites().addBackup() > .site("S") > .strategy(BackupConfiguration.BackupStrategy.ASYNC) > .conflictResolution(MyResover.class); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11802: ------------------------------- Sprint: DataGrid Sprint #44, DataGrid Sprint #45, DataGrid Sprint #46 (was: DataGrid Sprint #44, DataGrid Sprint #45) > Create SPI for Cross-Site Replication conflict resolution > --------------------------------------------------------- > > Key: ISPN-11802 > URL: https://issues.redhat.com/browse/ISPN-11802 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > A conflict happens if 2 sites try to update the same key (put/remove) concurrently. > With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update. > h2. Interface > {code:java} > interface ABC<V> { // or concrete class > String site(); //the site name which wrote this value > V value(); // the value. can be null if the key was removed > Metadata metadata(); //can be null > } > interface Resolve<K, V> { > ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2); > } > {code} > h2. Configuration > Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name. > For server mode, you need to add your jar with the classes required to {{server/lib}}. > The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy. > {code:java} > ConfigurationBuilder.sites().addBackup() > .site("S") > .strategy(BackupConfiguration.BackupStrategy.ASYNC) > .conflictResolution(MyResover.class); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12102) Validate configuration before storing it

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12102?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12102: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8535 > Validate configuration before storing it > ---------------------------------------- > > Key: ISPN-12102 > URL: https://issues.redhat.com/browse/ISPN-12102 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > Although {{ConfigurationBuilder}} does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running {{Transport}} to check if xsite is really supported. > As a side effect, the console is broken when you try to define the following cache without {{RELAY2}} being present in the JGroups stack. > {code:xml} > <infinispan> > <cache-container> > <distributed-cache name="xsite"> > <backups> > <backup site="site2"/> > </backups> > </distributed-cache> > </cache-container> > </infinispan> > {code} > This happens because the {{Configuration}} is stored and the {{Cache}} with the exception is stored as well. > The fix proposed it adds a method to {{ModuleLifecyle}} where the {{Configuration}} can be validated before it is store in the "global state". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12102) Validate configuration before storing it

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12102?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12102: ------------------------------- Status: Open (was: New) > Validate configuration before storing it > ---------------------------------------- > > Key: ISPN-12102 > URL: https://issues.redhat.com/browse/ISPN-12102 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > Although {{ConfigurationBuilder}} does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running {{Transport}} to check if xsite is really supported. > As a side effect, the console is broken when you try to define the following cache without {{RELAY2}} being present in the JGroups stack. > {code:xml} > <infinispan> > <cache-container> > <distributed-cache name="xsite"> > <backups> > <backup site="site2"/> > </backups> > </distributed-cache> > </cache-container> > </infinispan> > {code} > This happens because the {{Configuration}} is stored and the {{Cache}} with the exception is stored as well. > The fix proposed it adds a method to {{ModuleLifecyle}} where the {{Configuration}} can be validated before it is store in the "global state". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12102) Validate configuration before storing it

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-12102: ---------------------------------- Summary: Validate configuration before storing it Key: ISPN-12102 URL: https://issues.redhat.com/browse/ISPN-12102 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 11.0.1.Final Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 12.0.0.Dev01 Although {{ConfigurationBuilder}} does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running {{Transport}} to check if xsite is really supported. As a side effect, the console is broken when you try to define the following cache without {{RELAY2}} being present in the JGroups stack. {code:xml} <infinispan> <cache-container> <distributed-cache name="xsite"> <backups> <backup site="site2"/> </backups> </distributed-cache> </cache-container> </infinispan> {code} This happens because the {{Configuration}} is stored and the {{Cache}} with the exception is stored as well. The fix proposed it adds a method to {{ModuleLifecyle}} where the {{Configuration}} can be validated before it is store in the "global state". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HRJS-36) Implement SASL security features

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/HRJS-36?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant updated HRJS-36: -------------------------------- Fix Version/s: 12.0.0.Final > Implement SASL security features > -------------------------------- > > Key: HRJS-36 > URL: https://issues.redhat.com/browse/HRJS-36 > Project: Infinispan Javascript client > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Katia Aresti > Priority: Major > Fix For: 12.0.0.Final > > > EXTERNAL > PLAIN > DIGEST-MD5 > OAUTH > SCRAM > [https://github.com/jaredhanson/js-sasl] > https://github.com/legastero/js-sasl-scram-sha-1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12101) Add credential store support to the server

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-12101: -------------------------------------- Summary: Add credential store support to the server Key: ISPN-12101 URL: https://issues.redhat.com/browse/ISPN-12101 Project: Infinispan Issue Type: Enhancement Components: Security, Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 12.0.0.Final [http://docs.wildfly.org/20/WildFly_Elytron_Security.html#keystorecredenti...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 July 2020