September 2020 - infinispan-issues

[JBoss JIRA] (ISPN-12316) Convert expiration to no longer use transactions

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12316?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12316: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8683 > Convert expiration to no longer use transactions > ------------------------------------------------ > > Key: ISPN-12316 > URL: https://issues.redhat.com/browse/ISPN-12316 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > Currently when an entry is expired we remove it via the transactional mode of the cache, ie. if transaction we start a new transaction. We should instead always remove these elements in a non transactional way similar to putForExternalRead. This will make transaction processing much simpler as there is only one mode instead of 3+. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12316) Convert expiration to no longer use transactions

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12316?page=com.atlassian.jira.plugi... ] Will Burns reassigned ISPN-12316: --------------------------------- Assignee: Will Burns > Convert expiration to no longer use transactions > ------------------------------------------------ > > Key: ISPN-12316 > URL: https://issues.redhat.com/browse/ISPN-12316 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > Currently when an entry is expired we remove it via the transactional mode of the cache, ie. if transaction we start a new transaction. We should instead always remove these elements in a non transactional way similar to putForExternalRead. This will make transaction processing much simpler as there is only one mode instead of 3+. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12319) XSite Response should allow a value

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12319?page=com.atlassian.jira.plugi... ] Work on ISPN-12319 started by Will Burns. ----------------------------------------- > XSite Response should allow a value > ----------------------------------- > > Key: ISPN-12319 > URL: https://issues.redhat.com/browse/ISPN-12319 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > Currently cross site does not allow for a response. This will be needed for operations such as max idle cross site as we may have to know if a value has expired in the other site. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12319) XSite Response should allow a value

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12319?page=com.atlassian.jira.plugi... ] Will Burns reassigned ISPN-12319: --------------------------------- Assignee: Will Burns > XSite Response should allow a value > ----------------------------------- > > Key: ISPN-12319 > URL: https://issues.redhat.com/browse/ISPN-12319 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > Currently cross site does not allow for a response. This will be needed for operations such as max idle cross site as we may have to know if a value has expired in the other site. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12319) XSite Response should allow a value

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12319?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12319: ------------------------------ Status: Open (was: New) > XSite Response should allow a value > ----------------------------------- > > Key: ISPN-12319 > URL: https://issues.redhat.com/browse/ISPN-12319 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > Currently cross site does not allow for a response. This will be needed for operations such as max idle cross site as we may have to know if a value has expired in the other site. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12316) Convert expiration to no longer use transactions

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12316?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12316: ------------------------------ Status: Open (was: New) > Convert expiration to no longer use transactions > ------------------------------------------------ > > Key: ISPN-12316 > URL: https://issues.redhat.com/browse/ISPN-12316 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > > Currently when an entry is expired we remove it via the transactional mode of the cache, ie. if transaction we start a new transaction. We should instead always remove these elements in a non transactional way similar to putForExternalRead. This will make transaction processing much simpler as there is only one mode instead of 3+. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12319) XSite Response should allow a value

by Will Burns (Jira)

Will Burns created ISPN-12319: --------------------------------- Summary: XSite Response should allow a value Key: ISPN-12319 URL: https://issues.redhat.com/browse/ISPN-12319 Project: Infinispan Issue Type: Enhancement Components: Cross-Site Replication Reporter: Will Burns Fix For: 12.0.0.Final Currently cross site does not allow for a response. This will be needed for operations such as max idle cross site as we may have to know if a value has expired in the other site. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12318) Query.maxResult() ignored during entity loading

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12318?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12318: ------------------------------------- Description: When a query has a maxResult it should not try to load all results from the cache but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a large amount of garbage. Other issue is the default maxResult is not defined consistently: it is 10 for queries over REST and undefined for embedded and queries over Hot Rod. was: When a query has a maxResult it should not try to load all results from the cache but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. Other issue is the default maxResult is not defined consistently: it is 10 for queries over REST and undefined for embedded and queries over Hot Rod. > Query.maxResult() ignored during entity loading > ----------------------------------------------- > > Key: ISPN-12318 > URL: https://issues.redhat.com/browse/ISPN-12318 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 12.0.0.Dev03 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Critical > > When a query has a maxResult it should not try to load all results from the cache but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a large amount of garbage. > Other issue is the default maxResult is not defined consistently: it is 10 for queries over REST and undefined for embedded and queries over Hot Rod. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12318) Query.maxResult() ignored during entity loading

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-12318: ---------------------------------------- Summary: Query.maxResult() ignored during entity loading Key: ISPN-12318 URL: https://issues.redhat.com/browse/ISPN-12318 Project: Infinispan Issue Type: Bug Components: Embedded Querying Affects Versions: 12.0.0.Dev03 Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes When a query has a maxResult it should not try to load all results from the cache but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. Other issue is the default maxResult is not defined consistently: it is 10 for queries over REST and undefined for embedded and queries over Hot Rod. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-12317) WildFly modules integration tests do not start after surefire 3.0.0-M5 upgrade

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12317?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12317: -------------------------------- Status: Open (was: New) > WildFly modules integration tests do not start after surefire 3.0.0-M5 upgrade > ------------------------------------------------------------------------------ > > Key: ISPN-12317 > URL: https://issues.redhat.com/browse/ISPN-12317 > Project: Infinispan > Issue Type: Bug > Components: Build, Test Suite > Affects Versions: 12.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 12.0.0.Dev04 > > > The {{integrationtests/server-integration/wildfly-modules}} tests do not start because of a {{NoClassDefFoundError}}: > {noformat} > ./integrationtests/server-integration/wildfly-modules/target/failsafe-reports/2020-09-07T07-11-49_195-jvmRun1.dump > # Created at 2020-09-07T07:24:46.704 > java.lang.NoClassDefFoundError: org/infinispan/test/integration/as/client/AbstractHotRodClientIT > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1096) > at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:206) > at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:759) > at java.base/jdk.internal.loader.BuiltinClassLoader.findClassInModuleOrNull(BuiltinClassLoader.java:680) > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:605) > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) > at org.apache.maven.surefire.api.util.DefaultScanResult.loadClass(DefaultScanResult.java:136) > at org.apache.maven.surefire.api.util.DefaultScanResult.applyFilter(DefaultScanResult.java:100) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.scanClassPath(JUnitCoreProvider.java:292) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.setTestsToRun(JUnitCoreProvider.java:198) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:132) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162) > at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548) > Caused by: java.lang.ClassNotFoundException: org.infinispan.test.integration.as.client.AbstractHotRodClientIT > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) > ... 19 more > {noformat} > Further investigation shows that {{AbstractHotRodClientIT}} does exist on the classpath, but the classloader is trying to load it from the wrong jar: {{infinispan-wildfly-module-integrationtests-12.0.0-SNAPSHOT.jar}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2020