June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10332) Make sure listeners resume on the cpu thread

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10332?page=com.atlassian.jira.plugin... ] Will Burns reassigned ISPN-10332: --------------------------------- Assignee: Will Burns > Make sure listeners resume on the cpu thread > -------------------------------------------- > > Key: ISPN-10332 > URL: https://issues.jboss.org/browse/ISPN-10332 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Listeners can now be ran in a non blocking fashion. Unfortunately this means that they can complete on a completely unrelated thread, even possibly a user based thread. We need to make sure that we continue after a listener completes on the cpu thread to ensure we are doing processing correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10276) Adapt StoreMigrator to support Infinispan 8-10 marshallers

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10276?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10276: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Adapt StoreMigrator to support Infinispan 8-10 marshallers > ---------------------------------------------------------- > > Key: ISPN-10276 > URL: https://issues.jboss.org/browse/ISPN-10276 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > Currently the StoreMigrator only supports reading from Infinispan 8 stores. Due to the incompatibilities introduced with the Persistence marshaller changes, it's necessary for the migrator to now support reading from both 8/9 bytes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10335) Use stub for PersistenceManager when no stores are configured

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10335?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10335: ------------------------------ Status: Open (was: New) > Use stub for PersistenceManager when no stores are configured > ------------------------------------------------------------- > > Key: ISPN-10335 > URL: https://issues.jboss.org/browse/ISPN-10335 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Today even when no stores are configured we always use the PersistenceMangerImpl as a component. The interceptors that call it are never configured, however other key parts of the system such as state transfer still call into it. Currently PersistenceManagerImpl uses another thread for some operations until the new async store SPI can be introduced. By using a stub we won't have to worry about using another thread for such calls and the JVM should have less work to do in general. > Not to mention this should make the test suite run a bit better for tests that don't use a store. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10335) Use stub for PersistenceManager when no stores are configured

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10335?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10335: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7081 > Use stub for PersistenceManager when no stores are configured > ------------------------------------------------------------- > > Key: ISPN-10335 > URL: https://issues.jboss.org/browse/ISPN-10335 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Today even when no stores are configured we always use the PersistenceMangerImpl as a component. The interceptors that call it are never configured, however other key parts of the system such as state transfer still call into it. Currently PersistenceManagerImpl uses another thread for some operations until the new async store SPI can be introduced. By using a stub we won't have to worry about using another thread for such calls and the JVM should have less work to do in general. > Not to mention this should make the test suite run a bit better for tests that don't use a store. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10335) Use stub for PersistenceManager when no stores are configured

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10335?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10335: ------------------------------ Fix Version/s: 10.0.0.Beta4 > Use stub for PersistenceManager when no stores are configured > ------------------------------------------------------------- > > Key: ISPN-10335 > URL: https://issues.jboss.org/browse/ISPN-10335 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Today even when no stores are configured we always use the PersistenceMangerImpl as a component. The interceptors that call it are never configured, however other key parts of the system such as state transfer still call into it. Currently PersistenceManagerImpl uses another thread for some operations until the new async store SPI can be introduced. By using a stub we won't have to worry about using another thread for such calls and the JVM should have less work to do in general. > Not to mention this should make the test suite run a bit better for tests that don't use a store. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10332) Make sure listeners resume on the cpu thread

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10332?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10332: ------------------------------ Status: Open (was: New) > Make sure listeners resume on the cpu thread > -------------------------------------------- > > Key: ISPN-10332 > URL: https://issues.jboss.org/browse/ISPN-10332 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Listeners can now be ran in a non blocking fashion. Unfortunately this means that they can complete on a completely unrelated thread, even possibly a user based thread. We need to make sure that we continue after a listener completes on the cpu thread to ensure we are doing processing correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10332) Make sure listeners resume on the cpu thread

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10332?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10332: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7080 > Make sure listeners resume on the cpu thread > -------------------------------------------- > > Key: ISPN-10332 > URL: https://issues.jboss.org/browse/ISPN-10332 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Listeners can now be ran in a non blocking fashion. Unfortunately this means that they can complete on a completely unrelated thread, even possibly a user based thread. We need to make sure that we continue after a listener completes on the cpu thread to ensure we are doing processing correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10332) Make sure listeners resume on the cpu thread

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10332?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10332: ------------------------------ Fix Version/s: 10.0.0.Beta4 > Make sure listeners resume on the cpu thread > -------------------------------------------- > > Key: ISPN-10332 > URL: https://issues.jboss.org/browse/ISPN-10332 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Beta4 > > > Listeners can now be ran in a non blocking fashion. Unfortunately this means that they can complete on a completely unrelated thread, even possibly a user based thread. We need to make sure that we continue after a listener completes on the cpu thread to ensure we are doing processing correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10335) Use stub for PersistenceManager when no stores are configured

by Will Burns (Jira)

Will Burns created ISPN-10335: --------------------------------- Summary: Use stub for PersistenceManager when no stores are configured Key: ISPN-10335 URL: https://issues.jboss.org/browse/ISPN-10335 Project: Infinispan Issue Type: Sub-task Components: Core Reporter: Will Burns Assignee: Will Burns Today even when no stores are configured we always use the PersistenceMangerImpl as a component. The interceptors that call it are never configured, however other key parts of the system such as state transfer still call into it. Currently PersistenceManagerImpl uses another thread for some operations until the new async store SPI can be introduced. By using a stub we won't have to worry about using another thread for such calls and the JVM should have less work to do in general. Not to mention this should make the test suite run a bit better for tests that don't use a store. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10334) Prevent some tests to be running

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10334?page=com.atlassian.jira.plugin... ] Diego Lovison reassigned ISPN-10334: ------------------------------------ Assignee: Diego Lovison > Prevent some tests to be running > -------------------------------- > > Key: ISPN-10334 > URL: https://issues.jboss.org/browse/ISPN-10334 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 10.0.0.Beta3, 9.4.15.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > The Maven documentation says that we can prevent some tests to be running using: > mvn clean install -Dtest="*,!MyTest" > The problem is that it returns the following exception when executing: mvn verify -pl persistence/rocksdb -Dtest=*,!MyTest" > {noformat} > java.lang.NoClassDefFoundError: org/junit/rules/TestRule > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174) > at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:802) > at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:700) > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:623) > 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:521) > at org.apache.maven.surefire.util.DefaultScanResult.loadClass(DefaultScanResult.java:136) > at org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:100) > at org.apache.maven.surefire.testng.TestNGProvider.scanClassPath(TestNGProvider.java:235) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:136) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) > Caused by: java.lang.ClassNotFoundException: org.junit.rules.TestRule > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ... 17 more > {noformat} > If we add the junit dependecy in persistence/rocksdb/pom.xml it starts running the test but the filter is not applied. > Different filters were used in other to exclude that test but no one works. > I am proposing the PR in other to allow that behavior in ISPN -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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 June 2019