February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7117) ContinuousQuery.addContinuousQueryListener should fail if cache is async

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7117?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7117: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > ContinuousQuery.addContinuousQueryListener should fail if cache is async > ------------------------------------------------------------------------ > > Key: ISPN-7117 > URL: https://issues.jboss.org/browse/ISPN-7117 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7098) FunctionalDistributionTest.testDistributionFromPrimaryOwner random failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7098?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7098: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > FunctionalDistributionTest.testDistributionFromPrimaryOwner random failures > --------------------------------------------------------------------------- > > Key: ISPN-7098 > URL: https://issues.jboss.org/browse/ISPN-7098 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.3.0.Final > > > {{FunctionalDistributionTest.testDistributionFromPrimaryOwner}} assumes 100ms is enough for the command to be executed on both backup owners, but that's not always true -- e.g. when TRACE logging is enabled. > {noformat} > 15:27:36,079 TRACE (async-thread-Test-NodeC-p36570-t1:[]) [InvocationContextInterceptor] Invoked with command ReadWriteKeyCommand {key=testDistributionFromPrimaryOwner, flags=[]} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@44ffeec2] > 15:27:36,124 TRACE (async-thread-Test-NodeC-p36570-t1:[]) [JGroupsTransport] dests=[Test-NodeC-21089, Test-NodeD-31203], command=SingleRpcCommand{cacheName='dist', command=ReadWriteKeyCommand {key=testDistributionFromPrimaryOwner, flags=[]}}, mode=ASYNCHRONOUS, timeout=15000 > 15:27:36,140 TRACE (async-thread-Test-NodeC-p36570-t1:[]) [DefaultDataContainer] Store MetadataImmortalCacheEntry{key=testDistributionFromPrimaryOwner, value=1, metadata=MetaParamsInternalMetadata{params=MetaParams{metas=[]}}} in container > 15:27:36,144 TRACE (Incoming-1,Test-NodeD-31203:[]) [InvocationContextInterceptor] Invoked with command ReadWriteKeyCommand {key=testDistributionFromPrimaryOwner, flags=[]} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@73111d9] > 15:27:36,241 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.functional.FunctionalDistributionTest.testDistributionFromPrimaryOwner > java.lang.NullPointerException > at org.infinispan.functional.FunctionalDistributionTest.lambda$iterate$8(FunctionalDistributionTest.java:101) ~[test-classes/:?] > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_101] > at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) ~[?:1.8.0_101] > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_101] > at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) ~[?:1.8.0_101] > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) ~[?:1.8.0_101] > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[?:1.8.0_101] > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[?:1.8.0_101] > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_101] > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) ~[?:1.8.0_101] > at org.infinispan.functional.FunctionalDistributionTest.iterate(FunctionalDistributionTest.java:102) ~[test-classes/:?] > at org.infinispan.functional.FunctionalDistributionTest.doTestDistribution(FunctionalDistributionTest.java:80) ~[test-classes/:?] > at org.infinispan.functional.FunctionalDistributionTest.testDistributionFromPrimaryOwner(FunctionalDistributionTest.java:46) ~[test-classes/:?] > 15:27:36,259 TRACE (Incoming-1,Test-NodeD-31203:[]) [DefaultDataContainer] Store MetadataImmortalCacheEntry{key=testDistributionFromPrimaryOwner, value=1, metadata=MetaParamsInternalMetadata{params=MetaParams{metas=[]}}} in container > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7061) Allow using HOST header for routing in to REST interface

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7061?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7061: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Allow using HOST header for routing in to REST interface > -------------------------------------------------------- > > Key: ISPN-7061 > URL: https://issues.jboss.org/browse/ISPN-7061 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7624) Change CacheLoaderInterceptor to ignore in memory for certain operations when passivation is not enabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7624?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7624: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Change CacheLoaderInterceptor to ignore in memory for certain operations when passivation is not enabled > -------------------------------------------------------------------------------------------------------- > > Key: ISPN-7624 > URL: https://issues.jboss.org/browse/ISPN-7624 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Final > > > CacheLoader currently reads all in memory entries and then the store for bulk operations. This can be changed to only load from the store when passivation is not used as it should contain all entries that aren't in memory. > The only issue is that if Flag.SKIP_CACHE_STORE was used on a write. In this case we could store a boolean in the interceptor so that if this Flag is ever used we always do both. Very few users use this Flag and it should improve performance a bit and entries should be seen more consistently. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7606) DistributedExecutorMassIndexer.executeInternal should use an existing pool

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7606?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7606: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > DistributedExecutorMassIndexer.executeInternal should use an existing pool > -------------------------------------------------------------------------- > > Key: ISPN-7606 > URL: https://issues.jboss.org/browse/ISPN-7606 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Fix For: 9.3.0.Final > > > {{DistributedExecutorMassIndexer.executeInternal}} creates 2 executors: > 1. {{new DefaultExecutorService(cache)}} implicitly creates a single-threaded executor to run tasks on the local node. > 2. {{compositeFuture.whenCompleteAsync(consumer, Executors.newSingleThreadExecutor())}} explicitly creates a new single-threaded executor to run the consumer on. > Neither of these executors are shut down, and rather than complicating the code to stop them properly it would be better to use an existing executor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7600) Add Jolokia support for Managment Console

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7600?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7600: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Add Jolokia support for Managment Console > ----------------------------------------- > > Key: ISPN-7600 > URL: https://issues.jboss.org/browse/ISPN-7600 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > Fix For: 9.3.0.Final > > > The Management Console should be able to support Jolokia-enabled endpoints. This is required for supporting the console in Embedded Mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7553) Replicated cache with numOwners=1 doesn't send writes to backups

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7553?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7553: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Replicated cache with numOwners=1 doesn't send writes to backups > ---------------------------------------------------------------- > > Key: ISPN-7553 > URL: https://issues.jboss.org/browse/ISPN-7553 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 9.3.0.Final > > > {{BaseDistributionInterceptor.primaryReturnHandler()}} doesn't replicate writes to the backups if {{cacheConfiguration.clustering().hash().numOwners() == 1}}. That check is incorrect, because a segment can have more owners than configured: > 1. In a replicated cache, the configured {{numOwners}} is ignored, and all the members are owners. > 1. Even in a distributed cache, during rebalance, the segments being moved will have more than {{numOwners}} owners. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7475) Fixes for Hibernate 2LC integration with Infinispan 9

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7475?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7475: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Fixes for Hibernate 2LC integration with Infinispan 9 > ----------------------------------------------------- > > Key: ISPN-7475 > URL: https://issues.jboss.org/browse/ISPN-7475 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 9.3.0.Final > > > Umbrella JIRA for all issues found when integrating Hibernate 2LC with Infinispan 9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7470) Distributed executor does not fail over unless future.get() is called

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7470?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7470: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Distributed executor does not fail over unless future.get() is called > --------------------------------------------------------------------- > > Key: ISPN-7470 > URL: https://issues.jboss.org/browse/ISPN-7470 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.6.Final, 9.0.0.CR1 > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 9.3.0.Final > > > After ISPN-6392, {{DistributedExecutorService.submit(...)}} nominally returns a {{CompletableFuture}}. However, it doesn't behave like a regular {{CompletableFuture}}, because it doesn't run the failure policy until the user calls {{future.get()}}. > {{future.isComplete()}} will return {{true}} before running the failure policy, and {{future.whenComplete(callback)}} will also execute the callback before running the failure policy. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7415) Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7415?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7415: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata > -------------------------------------------------------------------------- > > Key: ISPN-7415 > URL: https://issues.jboss.org/browse/ISPN-7415 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > The default lifespan and maxIdle are -1 to signal no expiration, but calling {{EmbeddedMetadata.Builder.lifespan\(x)}} with any value will make it create an {{EmbeddedExpirableMetadata}} instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018