July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7958) Backports for 8.2.8.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7958?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7958: ---------------------------------- Fix Version/s: 8.2.9.Final (was: 8.2.8.Final) > Backports for 8.2.8.Final > ------------------------- > > Key: ISPN-7958 > URL: https://issues.jboss.org/browse/ISPN-7958 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.7.Final > Reporter: Radoslav Husar > Fix For: 8.2.9.Final > > > Tracking JIRA for issues to be backported to 8.2.x for 8.2.8.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7934) CacheImpl should consult EvictionStrategy#isEnabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7934?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7934: ---------------------------------- Fix Version/s: 8.2.9.Final (was: 8.2.8.Final) > CacheImpl should consult EvictionStrategy#isEnabled > --------------------------------------------------- > > Key: ISPN-7934 > URL: https://issues.jboss.org/browse/ISPN-7934 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.6.Final, 9.0.1.Final > Reporter: Galder Zamarreño > Assignee: Radoslav Husar > Fix For: 9.1.0.Final, 9.0.4.Final, 8.2.9.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6964) Flag is not included in Javadocs

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6964?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6964: ---------------------------------- Fix Version/s: 8.2.9.Final (was: 8.2.8.Final) > Flag is not included in Javadocs > -------------------------------- > > Key: ISPN-6964 > URL: https://issues.jboss.org/browse/ISPN-6964 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 8.2.4.Final, 9.0.0.Alpha4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.1.0.Final, 8.2.9.Final > > > The AdvancedCache javadocs refer to the Flag enumeration, but this is not included in the javadoc. Also DecoratedCache, which should be an internal implementation detail, is referenced as a public API. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8064) Javadocs are missing some packages

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8064?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8064: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks [~NadirX]! > Javadocs are missing some packages > ---------------------------------- > > Key: ISPN-8064 > URL: https://issues.jboss.org/browse/ISPN-8064 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 9.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.1.0.Final > > > The javadocs are missing some cachestores (rocksdb, soft-index), refer to HotRod instead of Hot Rod and include some spurious packages (scripting, commons-cdi) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7827) Additional Documentation for Cluster Executor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7827?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7827: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5191, https://github.com/infinispan/infinispan/pull/5292 (was: https://github.com/infinispan/infinispan/pull/5191) > Additional Documentation for Cluster Executor > --------------------------------------------- > > Key: ISPN-7827 > URL: https://issues.jboss.org/browse/ISPN-7827 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final > > > Cluster Executor has some additional API changes. We need to document these in the user guide. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8067) ClientClusterExpirationEventsTest.testSimpleExpired random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8067?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8067: -------------------------------- Status: Open (was: New) > ClientClusterExpirationEventsTest.testSimpleExpired random failures > ------------------------------------------------------------------- > > Key: ISPN-8067 > URL: https://issues.jboss.org/browse/ISPN-8067 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final, 9.1.1.Final > > Attachments: testSimpleExpire.zip > > > http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or... shows the failure. > What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked. > The easiest way to fix may be to just add another listener that waits for the entry to expire, thus making sure the event doesn't occur on another test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8067) ClientClusterExpirationEventsTest.testSimpleExpired random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8067?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8067: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5291 > ClientClusterExpirationEventsTest.testSimpleExpired random failures > ------------------------------------------------------------------- > > Key: ISPN-8067 > URL: https://issues.jboss.org/browse/ISPN-8067 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final, 9.1.1.Final > > Attachments: testSimpleExpire.zip > > > http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or... shows the failure. > What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked. > The easiest way to fix may be to just add another listener that waits for the entry to expire, thus making sure the event doesn't occur on another test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8067) ClientClusterExpirationEventsTest.testSimpleExpired random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8067?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8067: -------------------------------- Fix Version/s: 9.2.0.Final 9.1.1.Final > ClientClusterExpirationEventsTest.testSimpleExpired random failures > ------------------------------------------------------------------- > > Key: ISPN-8067 > URL: https://issues.jboss.org/browse/ISPN-8067 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final, 9.1.1.Final > > Attachments: testSimpleExpire.zip > > > http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or... shows the failure. > What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked. > The easiest way to fix may be to just add another listener that waits for the entry to expire, thus making sure the event doesn't occur on another test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8067) ClientClusterExpirationEventsTest.testSimpleExpired random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8067?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8067: -------------------------------- Description: http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or... shows the failure. What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked. The easiest way to fix may be to just add another listener that waits for the entry to expire, thus making sure the event doesn't occur on another test. was: http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or... shows the failure. What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked. > ClientClusterExpirationEventsTest.testSimpleExpired random failures > ------------------------------------------------------------------- > > Key: ISPN-8067 > URL: https://issues.jboss.org/browse/ISPN-8067 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: William Burns > Assignee: William Burns > Attachments: testSimpleExpire.zip > > > http://ci.infinispan.org/job/Infinispan/job/PR-5284/9/testReport/junit/or... shows the failure. > What happens is a RemoveExpired command from the testFilteringInCluster test can be seen in a later test. This is because testFilteringInCluster does not wait for the expiration event to be sent, because it is filtered out, so there is no way to tell when it is actually invoked. > The easiest way to fix may be to just add another listener that waits for the entry to expire, thus making sure the event doesn't occur on another test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4099) Local Listeners can raise entry events on rehash

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4099?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4099: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Local Listeners can raise entry events on rehash > ------------------------------------------------ > > Key: ISPN-4099 > URL: https://issues.jboss.org/browse/ISPN-4099 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 7.0.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final > > > -Cluster Listeners currently raise all create, modify and remove events. When a rehash event occurs this would cause a create event to be generated even though it wasn't just added to the cache. We need to not raise an event in this case.- > Writing up tests for this, cluster listeners are unaffected as they use the primaryOnly value for the listener. Further testing shows that this only affects local listeners when they become a backup owner from not being an owner. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017