March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7644) Administration console - loader tab allows to set invalid options

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7644: ------------------------------------ [~rmacor] The Asynch cache loader options shouldn't be explicitly be exposed to the user like they currently are. I will remove them from the dropdown. I was unable to reproduce your problem with "Single File Store". If I define the loader as a "Single File Store" on the default config, but I don't specify a store, then upon restart the loader is still defined as expected. > Administration console - loader tab allows to set invalid options > ----------------------------------------------------------------- > > Key: ISPN-7644 > URL: https://issues.jboss.org/browse/ISPN-7644 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Ryan Emerson > > Click on cache container -> cache -> configuration -> loader tab > Some options in loader type drop down such as "Async Cache loader" (but there might be more of them) result in following error, after cluster restart: > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datagrid-infinispan"), > ("cache-container" => "clustered"), > ("configurations" => "CONFIGURATIONS"), > ("distributed-cache-configuration" => "distributedCache") > ]) - failure description: "DGISPN0102: org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store" > Then there are valid options such as "Single File Store" which work if there is a corresponding cache store set up, in this case, File store. But if there isn't a cache store configured, the cache is no longer available after restart and configuration cannot be fixed from the console. > I suggest we add a restriction when configuring cache loaders in the console which wouldn't allow the users to configure cache loader without having to configure appropriate cache store first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7652) Incorrect River marshaller in server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7652?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-7652: ---------------------------------------- The same errors happening in 8.2.x are not appearing in master. This is most likely because master does not rely as heavily in JBoss Marshalling as a result of the new marshaller. Still, the same changes should be applied to master too since the server could be plugged with user classes that end up relying on JBoss Marshalling's River marshaller. > Incorrect River marshaller in server > ------------------------------------ > > Key: ISPN-7652 > URL: https://issues.jboss.org/browse/ISPN-7652 > Project: Infinispan > Issue Type: Task > Components: Marshalling, Server > Affects Versions: 8.2.6.Final, 9.0.0.CR3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR4, 8.2.7.Final > > > After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to force JBoss Marshaller's River to be in sync. As a result, the server currently ships River 1.4.10 version which causes issues mentioned [here|https://github.com/infinispan/infinispan/pull/4709] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7652) Incorrect River marshaller in server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7652?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7652: ----------------------------------- Affects Version/s: 9.0.0.CR3 > Incorrect River marshaller in server > ------------------------------------ > > Key: ISPN-7652 > URL: https://issues.jboss.org/browse/ISPN-7652 > Project: Infinispan > Issue Type: Task > Components: Marshalling, Server > Affects Versions: 8.2.6.Final, 9.0.0.CR3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR4, 8.2.7.Final > > > After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to force JBoss Marshaller's River to be in sync. As a result, the server currently ships River 1.4.10 version which causes issues mentioned [here|https://github.com/infinispan/infinispan/pull/4709] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7652) Incorrect River marshaller in server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7652?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7652: ----------------------------------- Fix Version/s: 9.0.0.CR4 > Incorrect River marshaller in server > ------------------------------------ > > Key: ISPN-7652 > URL: https://issues.jboss.org/browse/ISPN-7652 > Project: Infinispan > Issue Type: Task > Components: Marshalling, Server > Affects Versions: 8.2.6.Final, 9.0.0.CR3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR4, 8.2.7.Final > > > After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to force JBoss Marshaller's River to be in sync. As a result, the server currently ships River 1.4.10 version which causes issues mentioned [here|https://github.com/infinispan/infinispan/pull/4709] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7652) Incorrect River marshaller in server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7652?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7652: ----------------------------------- Status: Open (was: New) > Incorrect River marshaller in server > ------------------------------------ > > Key: ISPN-7652 > URL: https://issues.jboss.org/browse/ISPN-7652 > Project: Infinispan > Issue Type: Task > Components: Marshalling, Server > Affects Versions: 8.2.6.Final, 9.0.0.CR3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR4, 8.2.7.Final > > > After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to force JBoss Marshaller's River to be in sync. As a result, the server currently ships River 1.4.10 version which causes issues mentioned [here|https://github.com/infinispan/infinispan/pull/4709] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7652) Incorrect River marshaller in server

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-7652: -------------------------------------- Summary: Incorrect River marshaller in server Key: ISPN-7652 URL: https://issues.jboss.org/browse/ISPN-7652 Project: Infinispan Issue Type: Task Components: Marshalling, Server Affects Versions: 8.2.6.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 8.2.7.Final After upgrading JBoss Marshalling to 2.0.0.Beta3, we forgot to apply similar changes to force JBoss Marshaller's River to be in sync. As a result, the server currently ships River 1.4.10 version which causes issues mentioned [here|https://github.com/infinispan/infinispan/pull/4709] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7651) Add trace message when listener is invoked

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7651?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7651: -------------------------------- Status: Open (was: New) > Add trace message when listener is invoked > ------------------------------------------ > > Key: ISPN-7651 > URL: https://issues.jboss.org/browse/ISPN-7651 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Reporter: William Burns > Fix For: 9.0.0.CR4 > > > Currently when a local listener is invoked there is no message stating so. We should log a trace message so that we can see when a listener is invoked. This will help debug issues with users that use listeners as well as some tests that verify how often a listener is invoked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7651) Add trace message when listener is invoked

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7651?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7651: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5004 > Add trace message when listener is invoked > ------------------------------------------ > > Key: ISPN-7651 > URL: https://issues.jboss.org/browse/ISPN-7651 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Reporter: William Burns > Fix For: 9.0.0.CR4 > > > Currently when a local listener is invoked there is no message stating so. We should log a trace message so that we can see when a listener is invoked. This will help debug issues with users that use listeners as well as some tests that verify how often a listener is invoked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7651) Add trace message when listener is invoked

by William Burns (JIRA)

William Burns created ISPN-7651: ----------------------------------- Summary: Add trace message when listener is invoked Key: ISPN-7651 URL: https://issues.jboss.org/browse/ISPN-7651 Project: Infinispan Issue Type: Bug Components: Listeners Reporter: William Burns Fix For: 9.0.0.CR4 Currently when a local listener is invoked there is no message stating so. We should log a trace message so that we can see when a listener is invoked. This will help debug issues with users that use listeners as well as some tests that verify how often a listener is invoked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7650) Refactor tests to testng assertions

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7650?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-7650: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5003 > Refactor tests to testng assertions > ----------------------------------- > > Key: ISPN-7650 > URL: https://issues.jboss.org/browse/ISPN-7650 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Trivial > Labels: core-team > Fix For: 9.0.0.CR3 > > > Use testng assertions instead of assert in DistSyncFuncTest and APINonTxTest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017