March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8947) Upgrade to XStream 1.4.10

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8947?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8947: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5844 > Upgrade to XStream 1.4.10 > ------------------------- > > Key: ISPN-8947 > URL: https://issues.jboss.org/browse/ISPN-8947 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.2.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8947) Upgrade to XStream 1.4.10

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8947: --------------------------------------- Summary: Upgrade to XStream 1.4.10 Key: ISPN-8947 URL: https://issues.jboss.org/browse/ISPN-8947 Project: Infinispan Issue Type: Component Upgrade Components: Server Affects Versions: 9.2.0.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Fix For: 9.2.1.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8941) RemoteCacheAdmin configuration name should use cache name

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8941?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8941: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > RemoteCacheAdmin configuration name should use cache name > --------------------------------------------------------- > > Key: ISPN-8941 > URL: https://issues.jboss.org/browse/ISPN-8941 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Hot Rod, Server > Affects Versions: 9.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.1.Final > > > The current implementation of the server-side for remote cache admin expects the name of the configuration in the supplied XML to be "configuration" . This would be more intuitive if it used the actual name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8945) ClusterListenerDist(Tx)AddListener random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8945?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8945: ------------------------------- Description: There are 2 test methods that seem to like to fail for both the Tx and non tx tests. I can't seem to reproduce this after hours of running just the tests with or without logs and with reduced CPUs available. I also couldn't reproduce it running the entire test suite with and without tracing and reduced CPU or not. I am at a point to give up and just increase the timeouts. Currently these test expect 10s to be enough to add a new node and wait for a rebalance. The rebalance wait alone waits up to 60s. It doens't seem unreasonable therefore to just increase this to 30s. If it still fails afterwards there is some other issue most likely. https://ci.infinispan.org/job/Infinispan/job/master/505/testReport/ {noformat} java.lang.IllegalStateException: Thread already timed out waiting for event pre_add_listener_release_Cache 'cluster-listener'@ClusterListenerDistTxAddListenerTest-NodeA-45441 at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:175) at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:164) at org.infinispan.notifications.cachelistener.cluster.AbstractClusterListenerDistAddListenerTest.testMemberJoinsWhileClusterListenerInstalled(AbstractClusterListenerDistAddListenerTest.java:96) {noformat} was: There are 2 test methods that seem to like to fail for both the Tx and non tx tests. I can't seem to reproduce this after hours of running just the tests with or without logs and with reduced CPUs available. I also couldn't reproduce it running the entire test suite with and without tracing and reduced CPU or not. I am at a point to give up and just increase the timeouts. Currently these test expect 10s to be enough to add a new node and wait for a rebalance. The rebalance wait alone waits up to 60s. It doens't seem unreasonable therefore to just increase this to 30s. If it still fails afterwards there is some other issue most likely. https://ci.infinispan.org/job/Infinispan/job/master/505/testReport/ > ClusterListenerDist(Tx)AddListener random failures > -------------------------------------------------- > > Key: ISPN-8945 > URL: https://issues.jboss.org/browse/ISPN-8945 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.1.Final > > > There are 2 test methods that seem to like to fail for both the Tx and non tx tests. I can't seem to reproduce this after hours of running just the tests with or without logs and with reduced CPUs available. I also couldn't reproduce it running the entire test suite with and without tracing and reduced CPU or not. > I am at a point to give up and just increase the timeouts. Currently these test expect 10s to be enough to add a new node and wait for a rebalance. The rebalance wait alone waits up to 60s. It doens't seem unreasonable therefore to just increase this to 30s. If it still fails afterwards there is some other issue most likely. > https://ci.infinispan.org/job/Infinispan/job/master/505/testReport/ > {noformat} > java.lang.IllegalStateException: Thread already timed out waiting for event pre_add_listener_release_Cache 'cluster-listener'@ClusterListenerDistTxAddListenerTest-NodeA-45441 > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:175) > at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:164) > at org.infinispan.notifications.cachelistener.cluster.AbstractClusterListenerDistAddListenerTest.testMemberJoinsWhileClusterListenerInstalled(AbstractClusterListenerDistAddListenerTest.java:96) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8946) All collection wrappers should always delegate to underlying collections where available

by William Burns (JIRA)

William Burns created ISPN-8946: ----------------------------------- Summary: All collection wrappers should always delegate to underlying collections where available Key: ISPN-8946 URL: https://issues.jboss.org/browse/ISPN-8946 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.2.0.Final Reporter: William Burns Assignee: William Burns All places that override values returned from keySet and entrySet should always delegate appropriately to the underlying keySet or entrySet. We should try to be as minimally invasive to each level down as possible. An example would be that we shouldn't create copies of said collections if possible and instead just use delegates. https://github.com/infinispan/infinispan/pull/5794#discussion_r173789766 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8945) ClusterListenerDist(Tx)AddListener random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8945?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8945: -------------------------------- Status: Open (was: New) > ClusterListenerDist(Tx)AddListener random failures > -------------------------------------------------- > > Key: ISPN-8945 > URL: https://issues.jboss.org/browse/ISPN-8945 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.1.Final > > > There are 2 test methods that seem to like to fail for both the Tx and non tx tests. I can't seem to reproduce this after hours of running just the tests with or without logs and with reduced CPUs available. I also couldn't reproduce it running the entire test suite with and without tracing and reduced CPU or not. > I am at a point to give up and just increase the timeouts. Currently these test expect 10s to be enough to add a new node and wait for a rebalance. The rebalance wait alone waits up to 60s. It doens't seem unreasonable therefore to just increase this to 30s. If it still fails afterwards there is some other issue most likely. > https://ci.infinispan.org/job/Infinispan/job/master/505/testReport/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8945) ClusterListenerDist(Tx)AddListener random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8945?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8945: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5842 > ClusterListenerDist(Tx)AddListener random failures > -------------------------------------------------- > > Key: ISPN-8945 > URL: https://issues.jboss.org/browse/ISPN-8945 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.1.Final > > > There are 2 test methods that seem to like to fail for both the Tx and non tx tests. I can't seem to reproduce this after hours of running just the tests with or without logs and with reduced CPUs available. I also couldn't reproduce it running the entire test suite with and without tracing and reduced CPU or not. > I am at a point to give up and just increase the timeouts. Currently these test expect 10s to be enough to add a new node and wait for a rebalance. The rebalance wait alone waits up to 60s. It doens't seem unreasonable therefore to just increase this to 30s. If it still fails afterwards there is some other issue most likely. > https://ci.infinispan.org/job/Infinispan/job/master/505/testReport/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8945) ClusterListenerDist(Tx)AddListener random failures

by William Burns (JIRA)

William Burns created ISPN-8945: ----------------------------------- Summary: ClusterListenerDist(Tx)AddListener random failures Key: ISPN-8945 URL: https://issues.jboss.org/browse/ISPN-8945 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Affects Versions: 9.2.0.Final Reporter: William Burns Assignee: William Burns Fix For: 9.2.1.Final There are 2 test methods that seem to like to fail for both the Tx and non tx tests. I can't seem to reproduce this after hours of running just the tests with or without logs and with reduced CPUs available. I also couldn't reproduce it running the entire test suite with and without tracing and reduced CPU or not. I am at a point to give up and just increase the timeouts. Currently these test expect 10s to be enough to add a new node and wait for a rebalance. The rebalance wait alone waits up to 60s. It doens't seem unreasonable therefore to just increase this to 30s. If it still fails afterwards there is some other issue most likely. https://ci.infinispan.org/job/Infinispan/job/master/505/testReport/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8944) Maven profile traceTests no longer works

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8944?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-8944: ---------------------------------- Assignee: Dan Berindei > Maven profile traceTests no longer works > ---------------------------------------- > > Key: ISPN-8944 > URL: https://issues.jboss.org/browse/ISPN-8944 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: Dan Berindei > > When trying to run -PtraceTests for maven the tests print out this warning > ERROR StatusLogger File not found in file system or classpath: log4j2-trace.xml > We currently just pass log4j2-trace.xml. Unfortunately this file is no longer in the classpath and no module has that file relative to its directory. We need to add something for root-dir profiles it seems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8944) Maven profile traceTests no longer works

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8944?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8944: ------------------------------- Status: Open (was: New) > Maven profile traceTests no longer works > ---------------------------------------- > > Key: ISPN-8944 > URL: https://issues.jboss.org/browse/ISPN-8944 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: Dan Berindei > > When trying to run -PtraceTests for maven the tests print out this warning > ERROR StatusLogger File not found in file system or classpath: log4j2-trace.xml > We currently just pass log4j2-trace.xml. Unfortunately this file is no longer in the classpath and no module has that file relative to its directory. We need to add something for root-dir profiles it seems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018