[JBoss JIRA] (ISPN-6011) ClassCastException in CDI generated keys for JCache
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6011?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6011:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> ClassCastException in CDI generated keys for JCache
> ---------------------------------------------------
>
> Key: ISPN-6011
> URL: https://issues.jboss.org/browse/ISPN-6011
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.CR1, 8.0.2.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> When using JCache-annotations the DefaultCacheKeyGenerator exclusively looks at parameter values to form the cache key. Therefore it will be very likely that collissions occur (resulting in difficult to find ClassCastExceptions). The provided patch uses the method- and class names as additionally values to make the cache key more unique.
> Might also add that I am aware that by spec this should not be an issue when no cachename is given (as it should generate a cache using the class-name), but when a cache name is given collissions may occur.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-5929) InfinispanQueryIT.testQueryOnFirstNode random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-5929?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5929:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> InfinispanQueryIT.testQueryOnFirstNode random failures
> ------------------------------------------------------
>
> Key: ISPN-5929
> URL: https://issues.jboss.org/browse/ISPN-5929
> Project: Infinispan
> Issue Type: Bug
> Components: Integration , Test Suite - Query
> Affects Versions: 8.1.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Adrian Nistor
> Priority: Blocker
> Fix For: 9.4.8.Final
>
>
> {{InfinispanQueryIT.testQueryOnFirstNode()}} and {{InfinispanQueryIT.testQueryOnSecondNode()}} fail randomly in CI with this assertion:
> {noformat}
> java.lang.AssertionError: expected:<3> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.test.integration.as.query.InfinispanQueryIT.testQueryOnFirstNode(InfinispanQueryIT.java:99)
> {noformat}
> Example: http://ci.infinispan.org/viewLog.html?buildId=31810&tab=buildResultsDiv&b...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-5600) Optimize transactions on multiple caches
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-5600?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5600:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Optimize transactions on multiple caches
> ----------------------------------------
>
> Key: ISPN-5600
> URL: https://issues.jboss.org/browse/ISPN-5600
> Project: Infinispan
> Issue Type: Enhancement
> Components: Transactions
> Affects Versions: 8.0.0.Alpha2
> Reporter: Radim Vansa
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> NON_XA transactions that span multiple caches are registered as multiple synchronizations, and these synchronizations are often processed sequentially ^1^; therefore, we send synchronous PrepareCommand for each cache and then CommitCommand for each cache as well, delaying the commit by these round-trips.
> Since the targets for different caches may differ, we still need to send the RPCs separately, but in parallel. Therefore, there should be one uber-synchronization for all caches that use NON_XA mode (and maybe something similar with XA). I believe that using single synchronization could save some allocations, too.
> ^1^ Not sure if full-fledged JTA implementations do that; JTA spec does not say anything about the order of synchronizations and whether these should be processed in parallel.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-6094) Use security actions to read system properties for configuration
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6094?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6094:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Use security actions to read system properties for configuration
> ----------------------------------------------------------------
>
> Key: ISPN-6094
> URL: https://issues.jboss.org/browse/ISPN-6094
> Project: Infinispan
> Issue Type: Task
> Components: Core, Embedded Querying
> Affects Versions: 8.1.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> Infinispan uses system properties for out-of-band settings that weren't deemed important enough to have a proper configuration attribute:
> * infinispan.arrays.debug
> * infinispan.unsafe.force_multicast
> * infinispan.compat (obsolete?)
> * infinispan.debugDependencies
> * infinispan.stagger.delay (introduced with ISPN-825)
> * org.infinispan.query.indexmanager.LockAcquiringBackend.MAX_QUEUE_SIZE
> We should use a {{SecurityActions}} class to access these properties instead of {{Boolean.getBoolean()}} and {{Integer.getInteger()}}. We should also document these system properties, and evaluate moving them to the proper configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-6476) Integration test modules shouldn't change the failsafe plugin's lifecycle
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6476?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6476:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Integration test modules shouldn't change the failsafe plugin's lifecycle
> -------------------------------------------------------------------------
>
> Key: ISPN-6476
> URL: https://issues.jboss.org/browse/ISPN-6476
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 8.2.1.Final
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> Many of our integration tests modules run the {{integration-test}} and {{verify}} goals of {{maven-failsafe-plugin}} together, sometimes specifying a lifecycle phase, sometimes not. This shouldn't be necessary, because failsafe runs both goals, it just binds them to different phases.
> On the contrary, running both goals in the same phase can fail the build too early, skipping any executions bound to the {{post-integration-test}} phase.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-6470) CapacityFactorsFunctionalTest.testCapacityFactors random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6470?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6470:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> CapacityFactorsFunctionalTest.testCapacityFactors random failures
> ------------------------------------------------------------------
>
> Key: ISPN-6470
> URL: https://issues.jboss.org/browse/ISPN-6470
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 8.2.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.4.8.Final
>
>
> When nodes have different capacity factors, {{SyncConsistentHashFactory}} sometimes has trouble assigning the segments correctly:
> {noformat}
> java.lang.AssertionError: Expected between:<20.0> and:<50.0> but was:<52.0>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.infinispan.test.TestingUtil.assertBetween(TestingUtil.java:1455)
> at org.infinispan.distribution.ch.CapacityFactorsFunctionalTest.assertOwned(CapacityFactorsFunctionalTest.java:96)
> at org.infinispan.distribution.ch.CapacityFactorsFunctionalTest.testCapacityFactors(CapacityFactorsFunctionalTest.java:65)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-6448) ClassNotFoundException warnings in infinispan-rhq-plugin and infinispan-jcache-tck-runner build
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6448?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6448:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> ClassNotFoundException warnings in infinispan-rhq-plugin and infinispan-jcache-tck-runner build
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-6448
> URL: https://issues.jboss.org/browse/ISPN-6448
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> There are about 90 exceptions like this in total:
> {noformat}
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] 6550 [WARN] ClassFinder: From jar path org/infinispan/objectfilter/impl/ProtobufMatcher$1.class could not load class org.infinispan.objectfilter.impl.ProtobufMatcher$1
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] java.lang.ClassNotFoundException: org.infinispan.objectfilter.impl.ProtobufMatcher$1
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.Class.forName0(Native Method) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.Class.forName(Class.java:348) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.commons.util.Util.loadClassStrict(Util.java:171) ~[infinispan-commons.jar:9.0.0-SNAPSHOT]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.commons.util.ClassFinder.findClassesOnPath(ClassFinder.java:145) [infinispan-commons.jar:9.0.0-SNAPSHOT]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.commons.util.ClassFinder.infinispanClasses(ClassFinder.java:90) [infinispan-commons.jar:9.0.0-SNAPSHOT]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.tools.rhq.RhqPluginXmlGenerator.getMBeanClasses(RhqPluginXmlGenerator.java:117) [infinispan-tools.jar:9.0.0-SNAPSHOT]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.tools.rhq.RhqPluginXmlGenerator.start(RhqPluginXmlGenerator.java:75) [infinispan-tools.jar:9.0.0-SNAPSHOT]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:310) [tools.jar:?]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:189) [tools.jar:?]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:366) [tools.jar:?]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Start.begin(Start.java:219) [tools.jar:?]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Start.begin(Start.java:205) [tools.jar:?]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Main.execute(Main.java:64) [tools.jar:?]
> [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Main.main(Main.java:54) [tools.jar:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month