August 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12068) HTTP/2 pipeline missing chunked handler

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12068?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12068: ----------------------------------- Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48) > HTTP/2 pipeline missing chunked handler > ---------------------------------------- > > Key: ISPN-12068 > URL: https://issues.redhat.com/browse/ISPN-12068 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 11.0.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12111) Upgrade Hibernate Core/Search to 5.3.17.Final/5.10.7.Final

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12111?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12111: ----------------------------------- Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48) > Upgrade Hibernate Core/Search to 5.3.17.Final/5.10.7.Final > ---------------------------------------------------------- > > Key: ISPN-12111 > URL: https://issues.redhat.com/browse/ISPN-12111 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.19.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.20.Final > > > hibernate core =5.3.17.Final > hibernate search=5.10.7.Final > hibernate common=5.0.5.Final > hibernate hibernate-validator=6.0.20.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12030) BlockHound is not active on JDK 13/14

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12030?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12030: ----------------------------------- Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48) > BlockHound is not active on JDK 13/14 > ------------------------------------- > > Key: ISPN-12030 > URL: https://issues.redhat.com/browse/ISPN-12030 > Project: Infinispan > Issue Type: Bug > Components: Build, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final, 11.0.1.Final > > > BlockHound cannot instrument native methods on JDK 13+ > {noformat} > 15:04:47,001 FATAL (Thread-0) [Infinispan-TEST] Throwable was not caught in thread Thread[Thread-0,5,main] - exception is: java.lang.IllegalStateException: The instrumentation have failed. > It looks like you're running on JDK 13+. > You need to add '-XX:+AllowRedefinitionToAddDeleteMethods' JVM flag. > See https://github.com/reactor/BlockHound/issues/33 for more info. > {noformat} > Maven profile {{java13-test}} is supposed to add flag -XX:+AllowRedefinitionToAddDeleteMethods to the fork JVM, but it doesn't work because the activation condition is incomplete (missing a {{)}} after the comma). > The profile also tries to add the flag when the {{java8-test}} profile is selected from the command line, so adding the missing {{)}} is not enough. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11336?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11336: ----------------------------------- Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48) > 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12014) Upgrade mojo-executor

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12014?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12014: ----------------------------------- Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48) > Upgrade mojo-executor > --------------------- > > Key: ISPN-12014 > URL: https://issues.redhat.com/browse/ISPN-12014 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 11.0.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.1.Final > > > Upgrade mojo-executor to 2.3.1 > Also, upgrade its transitive dependencies: > * Maven-Core to 3.5.4 > * Plexus-utils to 3.1.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12018) Fix JpaStoreCompatibilityTest failure

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12018?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12018: ----------------------------------- Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48) > Fix JpaStoreCompatibilityTest failure > ------------------------------------- > > Key: ISPN-12018 > URL: https://issues.redhat.com/browse/ISPN-12018 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.1.Final > > > jboss-parent uses a different {{java.io.tmpdir}} to run the tests. When the JPA test suite is built, the {{persistence.xml}} file is configured with {{java.io.tmpdir=/tmp}} but when it runs, {{java.io.tmpdir=.../target/}} folder. > The test is unable to find the 10.1x data and it fails. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11802: ----------------------------------- Fix Version/s: 12.0.0.Dev03 (was: 12.0.0.Dev02) > 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.Dev03 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12230) Deprecate client keySizeEstimate and valueSizeEstimate attributes

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12230?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12230: ----------------------------------- Fix Version/s: 12.0.0.Dev03 (was: 12.0.0.Dev02) > Deprecate client keySizeEstimate and valueSizeEstimate attributes > ----------------------------------------------------------------- > > Key: ISPN-12230 > URL: https://issues.redhat.com/browse/ISPN-12230 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Hot Rod > Affects Versions: 11.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev03 > > > The core configuration has long ago removed the {{keySizeEstimate}} and {{valueSizeEstimate}} attributes, using instead a {{BufferSizePredictor}} to dynamically estimate the size of the next key/value. {{ProtostreamMarshaller}} goes even further and ignores the estimate. > We should stop using {{keySizeEstimate}} and {{valueSizeEstimate}} on the client as well, and instead use a fixed buffer size ({{ProtostreamMarshaller}} uses 512). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12151) Add error count metric

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12151?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12151: ----------------------------------- Fix Version/s: 12.0.0.Dev03 (was: 12.0.0.Dev02) > Add error count metric > ---------------------- > > Key: ISPN-12151 > URL: https://issues.redhat.com/browse/ISPN-12151 > Project: Infinispan > Issue Type: Feature Request > Components: Analytics > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final, 12.0.0.Dev03 > > > {{CacheMgmtInterceptor}} has metrics for the different kind of key operations, but errors are not tracked. We should add a metric to count errors, and perhaps a histogram for the duration of failed invocations as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12092) Make the welcome visible without login in every case

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12092?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12092: ----------------------------------- Fix Version/s: 12.0.0.Dev03 (was: 12.0.0.Dev02) > Make the welcome visible without login in every case > ---------------------------------------------------- > > Key: ISPN-12092 > URL: https://issues.redhat.com/browse/ISPN-12092 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 11.0.1.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Minor > Fix For: 12.0.0.Dev03 > > > With keycloak integration, the welcome page detects the login into keycloak. > * Welcome page visible without login > * If Keycloak, when clicking the button, we land into keycloak login > * If Http, we go into the login endpoint > * If http but no user, pop up explaining you need to create a user > * If there is no auth or the server down, go to the console > -- This message was sent by Atlassian Jira (v7.13.8#713008)

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