March 2018 - infinispan-issues - Jboss List Archives

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

by William Burns (JIRA)

William Burns created ISPN-8944: ----------------------------------- Summary: 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 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-8943) Update to XStream 1.4.10

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8943: --------------------------------------- Summary: Update to XStream 1.4.10 Key: ISPN-8943 URL: https://issues.jboss.org/browse/ISPN-8943 Project: Infinispan Issue Type: Component Upgrade Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3968) Intermittent test failure: CacheLoaderFunctionalTest.testPurgeOnStartup

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3968?page=com.atlassian.jira.plugin.... ] Sanne Grinovero closed ISPN-3968. --------------------------------- Resolution: Out of Date > Intermittent test failure: CacheLoaderFunctionalTest.testPurgeOnStartup > ----------------------------------------------------------------------- > > Key: ISPN-3968 > URL: https://issues.jboss.org/browse/ISPN-3968 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Sanne Grinovero > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2998) NPE on shutdown: ExternalizerTableProxy already cleared

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2998?page=com.atlassian.jira.plugin.... ] Sanne Grinovero closed ISPN-2998. --------------------------------- Resolution: Out of Date > NPE on shutdown: ExternalizerTableProxy already cleared > ------------------------------------------------------- > > Key: ISPN-2998 > URL: https://issues.jboss.org/browse/ISPN-2998 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.5.Final > Reporter: Sanne Grinovero > Assignee: Galder Zamarreño > Priority: Minor > > Apparently the method > {code}org.infinispan.marshall.jboss.JBossMarshaller.ExternalizerTableProxy.getObjectWriter(Object){code} > can be invoked during shutdown even when _externalizerTable_ is null, generating an NPE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8942) Joiners may miss registered listener

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-8942: --------------------------------- Summary: Joiners may miss registered listener Key: ISPN-8942 URL: https://issues.jboss.org/browse/ISPN-8942 Project: Infinispan Issue Type: Bug Components: Listeners Reporter: Pedro Ruivo Assignee: Pedro Ruivo Since the change where the cluster listener registration is send to the cache-members, the following scenario can happen: {noformat} [NODE_C] 2018-03-14 12:19:23,823 -> received topology with {A,B}. requests listeners from A [NODE_D] 2018-03-14 12:19:23,824 -> received topology with {A,B}. requests listeners from A [NODE_B] 2018-03-14 12:19:23,926 -> register cluster listener A, B [NODE_A] 2018-03-14 12:19:23,931 -> register cluster listener from B {noformat} Possible fix is to fetch the cluster listener when it is member of the topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8942) Joiners may miss registered listener

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8942?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8942: ------------------------------ Status: Open (was: New) > Joiners may miss registered listener > ------------------------------------ > > Key: ISPN-8942 > URL: https://issues.jboss.org/browse/ISPN-8942 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Since the change where the cluster listener registration is send to the cache-members, the following scenario can happen: > {noformat} > [NODE_C] 2018-03-14 12:19:23,823 -> received topology with {A,B}. requests listeners from A > [NODE_D] 2018-03-14 12:19:23,824 -> received topology with {A,B}. requests listeners from A > [NODE_B] 2018-03-14 12:19:23,926 -> register cluster listener A, B > [NODE_A] 2018-03-14 12:19:23,931 -> register cluster listener from B > {noformat} > Possible fix is to fetch the cluster listener when it is member of the topology. -- 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 Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8941?page=com.atlassian.jira.plugin.... ] Work on ISPN-8941 started by Tristan Tarrant. --------------------------------------------- > 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-8941) RemoteCacheAdmin configuration name should use cache name

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8941?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8941: ---------------------------------- Status: Open (was: New) > 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-8941) RemoteCacheAdmin configuration name should use cache name

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8941?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8941: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5840 > 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-8941) RemoteCacheAdmin configuration name should use cache name

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8941: ------------------------------------- Summary: 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018