October 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7033) Convert Spring testsuite from TestNG to JUnit

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7033?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-7033: ----------------------------------------- Assignee: Sebastian Łaskawiec > Convert Spring testsuite from TestNG to JUnit > --------------------------------------------- > > Key: ISPN-7033 > URL: https://issues.jboss.org/browse/ISPN-7033 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7110) Async invocation stages should use CompletableFutures.await()

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7110?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7110: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4614 > Async invocation stages should use CompletableFutures.await() > ------------------------------------------------------------- > > Key: ISPN-7110 > URL: https://issues.jboss.org/browse/ISPN-7110 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1 > > > As described in ISPN-5962, {{CompletableFuture.get()}} and {{CompletableFuture.join()}} without a timeout do a lot of spinning, so we need to use {{CompletableFutures.await(CompletableFuture)}} instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7110) Async invocation stages should use CompletableFutures.await()

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7110: ---------------------------------- Summary: Async invocation stages should use CompletableFutures.await() Key: ISPN-7110 URL: https://issues.jboss.org/browse/ISPN-7110 Project: Infinispan Issue Type: Bug Components: Core Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Beta1 As described in ISPN-5962, {{CompletableFuture.get()}} and {{CompletableFuture.join()}} without a timeout do a lot of spinning, so we need to use {{CompletableFutures.await(CompletableFuture)}} instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7110) Async invocation stages should use CompletableFutures.await()

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7110?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7110: ------------------------------- Status: Open (was: New) > Async invocation stages should use CompletableFutures.await() > ------------------------------------------------------------- > > Key: ISPN-7110 > URL: https://issues.jboss.org/browse/ISPN-7110 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1 > > > As described in ISPN-5962, {{CompletableFuture.get()}} and {{CompletableFuture.join()}} without a timeout do a lot of spinning, so we need to use {{CompletableFutures.await(CompletableFuture)}} instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7074) Indexed entities inheritance does not copy set

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7074?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7074: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Indexed entities inheritance does not copy set > ---------------------------------------------- > > Key: ISPN-7074 > URL: https://issues.jboss.org/browse/ISPN-7074 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1, 9.0.0.Final, 8.2.5.Final > > > The indexed entities configuration attribute does not provide a copier so, in the case of inheritance, all configurations share the same set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7063) FunctionalCachestoreTest and FunctionalInMemoryTest random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7063?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7063: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > FunctionalCachestoreTest and FunctionalInMemoryTest random failures > ------------------------------------------------------------------- > > Key: ISPN-7063 > URL: https://issues.jboss.org/browse/ISPN-7063 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Radim Vansa > Labels: testsuite_stability > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > ISPN-6586 introduced a static field in {{invocationCount}} that is shared by {{FunctionalInMemoryTest}} and {{FunctionalCachestoreTest}}. When they run in parallel, the counter is no longer deterministic and they both fail randomly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7102) Eviction is not correctly handled in case of local reads

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-7102?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-7102: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1383916 Bugzilla Update: Perform > Eviction is not correctly handled in case of local reads > -------------------------------------------------------- > > Key: ISPN-7102 > URL: https://issues.jboss.org/browse/ISPN-7102 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Wolf-Dieter Fink > Assignee: William Burns > > If entries are accessed by get only the cache read will not update the entry correct and the eviction is affected if the cache becomes full. > This seems to affect the LIRS policy more than LRU -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7105) Expiration is not working under some circumstances with AtomicMap

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-7105?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-7105: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1383945 Bugzilla Update: Perform > Expiration is not working under some circumstances with AtomicMap > ----------------------------------------------------------------- > > Key: ISPN-7105 > URL: https://issues.jboss.org/browse/ISPN-7105 > Project: Infinispan > Issue Type: Bug > Components: Core > Environment: AtomicMap, write-skew, transactional > Reporter: Wolf-Dieter Fink > Attachments: jdg-ws-am-lifespan-reproducer.zip > > > When AtomicMaps are used with writeskew (+ simple versioning) lifespan from the config file is ignored and instead get infinite lifespan for the entries. > The configured default value is used if I any of the following parameters change > - Disable write skew checks > - Use a normal put (not atomic maps) > - Do not start transactions first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7104) Cache remove fails to return value in invalidation mode with cache store

by Vladimir Dzhuvinov (JIRA)

[ https://issues.jboss.org/browse/ISPN-7104?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov commented on ISPN-7104: ------------------------------------------ Plus *putIfAbsent*. > Cache remove fails to return value in invalidation mode with cache store > ------------------------------------------------------------------------ > > Key: ISPN-7104 > URL: https://issues.jboss.org/browse/ISPN-7104 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Priority: Critical > Attachments: RemoveInInvalidationModeTest.java > > > The cache `remove` method occasionally fails to return the removed value, and returns `null`. > Observed in two node setup in invalidation mode, with a configured cache store (Redis). > Tests reveal that about 40% of the times the method returns `null`, the remaining 60% the removed value is correctly returned. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7104) Cache remove fails to return value in invalidation mode with cache store

by Vladimir Dzhuvinov (JIRA)

[ https://issues.jboss.org/browse/ISPN-7104?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov commented on ISPN-7104: ------------------------------------------ Just found out that *replace(key,value)* is also affected. In tests it succeed about 37% of the time, for the remaining calls it returned null. > Cache remove fails to return value in invalidation mode with cache store > ------------------------------------------------------------------------ > > Key: ISPN-7104 > URL: https://issues.jboss.org/browse/ISPN-7104 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Priority: Critical > Attachments: RemoveInInvalidationModeTest.java > > > The cache `remove` method occasionally fails to return the removed value, and returns `null`. > Observed in two node setup in invalidation mode, with a configured cache store (Redis). > Tests reveal that about 40% of the times the method returns `null`, the remaining 60% the removed value is correctly returned. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016