[JBoss JIRA] (ISPN-9463) Provide API to enlist the resource with TransactionManager
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9463?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9463:
----------------------------------
Fix Version/s: 10.0.0.Beta2
(was: 10.0.0.Beta1)
> Provide API to enlist the resource with TransactionManager
> ----------------------------------------------------------
>
> Key: ISPN-9463
> URL: https://issues.jboss.org/browse/ISPN-9463
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod, Remote Protocols, Transactions
> Reporter: Ramesh Reddy
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 10.0.0.Beta2
>
>
> Currently, Infinispan will automatically enlist the transaction when a transaction is bound to the executing thread. However, in cases like Teiid where remote access to Infinispan access is wrapped with a resource-adapter (RAR) the resource adapter does the explicit enlisting or delisting. For this there needs to be API provided by Infinispan Cache like
> {code}
> RemoteCacheManager.getXaResource()
> {code}
> where it can access the XA resource.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9621) Split global marshaller into Persistence and Internal marshaller
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9621?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9621:
----------------------------------
Fix Version/s: 10.0.0.Beta2
(was: 10.0.0.Beta1)
> Split global marshaller into Persistence and Internal marshaller
> ----------------------------------------------------------------
>
> Key: ISPN-9621
> URL: https://issues.jboss.org/browse/ISPN-9621
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta2
>
>
> Currently the internal marshaller is used for marshalling key/value/metadata in store implementations. This means that it is possible for internal classes to be marshalled to a user store, which can cause compatibility issues if an internal classes serialization format changes (due to marshaller changes or addition/removal of fields).
> We should separate the internal and persistence marshaller, only exposing the latter to stores via the InitializationContext. The persistence marshaller should only be able to serialize user key/values and the metadata/version data.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9620:
----------------------------------
Fix Version/s: 10.0.0.Beta2
(was: 10.0.0.Beta1)
> Rolling Upgrade Marshaller Changes
> ----------------------------------
>
> Key: ISPN-9620
> URL: https://issues.jboss.org/browse/ISPN-9620
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta2
>
>
> In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-2575) Key Transformer registration is required on all nodes of the cluster, in case of custom keys
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2575:
----------------------------------
Fix Version/s: 10.0.0.Beta2
(was: 10.0.0.Beta1)
> Key Transformer registration is required on all nodes of the cluster, in case of custom keys
> --------------------------------------------------------------------------------------------
>
> Key: ISPN-2575
> URL: https://issues.jboss.org/browse/ISPN-2575
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Affects Versions: 5.2.0.Beta5
> Reporter: Anna Manukyan
> Assignee: Adrian Nistor
> Priority: Minor
> Fix For: 10.0.0.Beta2
>
> Attachments: ClusteredCacheTest.java
>
>
> The case is the following:
> I have a clustered cache on which I want to perform a search. I'm doing the following:
> I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception:
> java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer
> When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager.
> The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer()
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9954) Missing dependency on server/integration/testsuite
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9954?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9954:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.4.7.Final
(was: 9.4.8.Final)
Resolution: Done
> Missing dependency on server/integration/testsuite
> --------------------------------------------------
>
> Key: ISPN-9954
> URL: https://issues.jboss.org/browse/ISPN-9954
> Project: Infinispan
> Issue Type: Bug
> Components: Dependency, Test Suite - Server
> Affects Versions: 9.4.6.Final
> Reporter: Gustavo Lira
> Assignee: Gustavo Lira
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.7.Final
>
>
> infinispan-remote dependecy is missing when we try to build infinispan using the following command
> {code}mvn -s settings_mead_jdg.xml -f infinispan/pom.xml -pl server/integration/testsuite -B clean verify -Dmaven.test.failure.ignore=true -Pclient.hotrod.osgi -Dversion.karaf=4.2.0 -Dzip.dist=/path/to/infinispan-server.zip {code}
> Here the throwed exception
> {noformat}
> [INFO] Running org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT
> [OK: 0, KO: 0, SKIP: 0] Test starting: RemoteCacheOsgiIT.initializationError
> [OK: 0, KO: 1, SKIP: 0] Test failed: RemoteCacheOsgiIT.initializationError
> org.ops4j.pax.exam.TestContainerException: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project?
> at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:195)
> at org.ops4j.pax.exam.junit.impl.ProbeRunner.<init>(ProbeRunner.java:78)
> at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
> at org.ops4j.pax.exam.junit.PaxExam.<init>(PaxExam.java:73)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
> at org.junit.runner.Computer.getRunner(Computer.java:40)
> at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
> at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
> at org.junit.runners.Suite.<init>(Suite.java:81)
> at org.junit.runner.Computer.getSuite(Computer.java:28)
> at org.junit.runner.Request.classes(Request.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:126)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> 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.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project?
> at org.ops4j.pax.exam.MavenUtils.getArtifactVersion(MavenUtils.java:75)
> at org.ops4j.pax.exam.MavenUtils$1.getVersion(MavenUtils.java:109)
> at org.ops4j.pax.exam.options.MavenArtifactUrlReference.version(MavenArtifactUrlReference.java:86)
> at org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(MavenArtifactUrlReference.java:90)
> at org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT.config(RemoteCacheOsgiIT.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:248)
> at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
> ... 28 more
> 07:31:08.257 [main] ERROR org.infinispan.commons.test.TestSuiteProgress - Test failed: RemoteCacheOsgiIT.initializationError
> org.ops4j.pax.exam.TestContainerException: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project?
> at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:195) ~[pax-exam-spi-4.11.0.jar:?]
> at org.ops4j.pax.exam.junit.impl.ProbeRunner.<init>(ProbeRunner.java:78) ~[pax-exam-junit4-4.11.0.jar:?]
> at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82) ~[pax-exam-junit4-4.11.0.jar:?]
> at org.ops4j.pax.exam.junit.PaxExam.<init>(PaxExam.java:73) ~[pax-exam-junit4-4.11.0.jar:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_191]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_191]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_191]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_191]
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runner.Computer.getRunner(Computer.java:40) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runner.Computer$1.runnerForClass(Computer.java:31) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runners.Suite.<init>(Suite.java:81) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runner.Computer.getSuite(Computer.java:28) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.junit.runner.Request.classes(Request.java:75) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:126) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) [surefire-booter-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) [surefire-booter-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) [surefire-booter-3.0.0-M1.jar:3.0.0-M1]
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) [surefire-booter-3.0.0-M1.jar:3.0.0-M1]
> Caused by: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project?
> at org.ops4j.pax.exam.MavenUtils.getArtifactVersion(MavenUtils.java:75) ~[pax-exam-4.11.0.jar:?]
> at org.ops4j.pax.exam.MavenUtils$1.getVersion(MavenUtils.java:109) ~[pax-exam-4.11.0.jar:?]
> at org.ops4j.pax.exam.options.MavenArtifactUrlReference.version(MavenArtifactUrlReference.java:86) ~[pax-exam-4.11.0.jar:?]
> at org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(MavenArtifactUrlReference.java:90) ~[pax-exam-4.11.0.jar:?]
> at org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT.config(RemoteCacheOsgiIT.java:83) ~[test-classes/:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_191]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_191]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_191]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_191]
> at org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:248) ~[pax-exam-spi-4.11.0.jar:?]
> at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184) ~[pax-exam-spi-4.11.0.jar:?]
> ... 28 more
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.037 s <<< FAILURE! - in org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT
> [ERROR] initializationError(org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT) Time elapsed: 0.008 s <<< ERROR!
> org.ops4j.pax.exam.TestContainerException: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project?
> at org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT.config(RemoteCacheOsgiIT.java:83)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9933) Cache components are not stopped after startup error
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9933?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9933:
----------------------------------
Fix Version/s: 10.0.0.Beta2
(was: 10.0.0.Beta1)
> Cache components are not stopped after startup error
> ----------------------------------------------------
>
> Key: ISPN-9933
> URL: https://issues.jboss.org/browse/ISPN-9933
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta2, 9.4.8.Final
>
>
> When a cache fails to start (e.g. because a store is not available on startup), the cache is not registered in {{DefaultCacheManager's}} map, and stopping the cache manager does not stop any of the components that already started (or even the component that failed).
> E.g. in {{NonStringKeyPreloadTest}}, the store is not available on startup, and the threads created by HikariCP on startup (in 9.4.x) are not released. The test also leaks an Agroal thread on master, but that is because the test is keeping the connection pool factory in a static field.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month