March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7640) Upgrade to Netty 4.1.9

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7640?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7640: ------------------------------- Fix Version/s: 9.0.0.CR4 > Upgrade to Netty 4.1.9 > ---------------------- > > Key: ISPN-7640 > URL: https://issues.jboss.org/browse/ISPN-7640 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.CR4, 9.0.0.Final, 8.2.7.Final > > > More details on https://github.com/netty/netty/issues/6443#issuecomment-282481345 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7640) Upgrade to Netty 4.1.9

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7640?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7640: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to Netty 4.1.9 > ---------------------- > > Key: ISPN-7640 > URL: https://issues.jboss.org/browse/ISPN-7640 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Final, 8.2.7.Final > > > More details on https://github.com/netty/netty/issues/6443#issuecomment-282481345 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7572) Infinispan initialization via DirectoryProvider can't use any CacheStore or other extensions

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7572?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7572: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4974, https://github.com/infinispan/infinispan/pull/4999, https://github.com/infinispan/infinispan/pull/4981 (was: https://github.com/infinispan/infinispan/pull/4974) > Infinispan initialization via DirectoryProvider can't use any CacheStore or other extensions > -------------------------------------------------------------------------------------------- > > Key: ISPN-7572 > URL: https://issues.jboss.org/browse/ISPN-7572 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Lucene Directory, WildFly modules > Affects Versions: 8.2.6.Final, 9.0.0.CR2 > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 9.0.0.Final, 8.2.7.Final > > > When the Infinispan CacheManager is bootstrapped via Hibernate Search, the Infinispan modules are not necessarily visible to the deployment classpath (the TCCL). > In this case if the configuration file refers to any extension such as a {{CacheStore}}, Infinispan will fail to start as it doesn't depend on the modules of its extensions. > This will cause puzzling errors such as : > {{ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace 'urn:infinispan:config:store:jdbc:8.0'. Check that your configuration is up-to date for this version of Infinispan.}} > For the record, the fact that the configuration parser expects to use the TCCL is an old problem which I've highlighted already in the past: > Explicit classloader support during parsing was introduced in 2013: > - http://lists.jboss.org/pipermail/infinispan-dev/2013-April/012590.html > Then removed again in 2014: > - http://lists.jboss.org/pipermail/infinispan-dev/2014-May/014952.html > I asked for improvements and hoped for someone to take ownership: > - http://lists.jboss.org/pipermail/infinispan-dev/2014-October/015549.html > In this last email I explained what Hibernate Search would do, in lack of better alternatives..and so we did. > Finally, this component of Hibernate Search code was transferred to the Infinispan repository so luckily we can change both components as you see most fit; the only requirement is to not expect the Hibernate users to have Infinispan on their TCCL. > My proposal is simple: the Infinispan-core module should have an optional dependency to its extensions, including at least all supported CacheStore implementations so that people can use them. > In fact, I expected them to do as it feels natural to have a graph edge towards extension points to be able to load them. > But [~NadirX] doesn't like that, so assigning the issue to him ;-) > Alternative ideas: > * allow people to mention module names explicitly in the Infinispan configuration? > * have a module which bootstraps the CacheManager, depending explicitly on all extensions, and register it over JNDI > I favour the second option, especially as it came up before as a dire pratical need for many other situations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7657) Administration console - Indexing tab allows invalid configuration to be set

by Roman Macor (JIRA)

Roman Macor created ISPN-7657: --------------------------------- Summary: Administration console - Indexing tab allows invalid configuration to be set Key: ISPN-7657 URL: https://issues.jboss.org/browse/ISPN-7657 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.CR3 Reporter: Roman Macor Setting indexing for invalidation cache is not a valid configuration, but the console allows this configuration. Part of the server log after restart: ... org.infinispan.commons.CacheConfigurationException: ISPN000273: Indexing can not be enabled on caches in Invalidation mode ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7585) Rolling Upgrade overrides changed data in the target cluster

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7585?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes resolved ISPN-7585. ------------------------------------- Resolution: Duplicate > Rolling Upgrade overrides changed data in the target cluster > ------------------------------------------------------------ > > Key: ISPN-7585 > URL: https://issues.jboss.org/browse/ISPN-7585 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha1, 8.2.6.Final > Reporter: Gustavo Fernandes > Labels: rolling_upgrade > > Let (K,V) be an entry in the source cluster, any update to K in the target cluster will get overridden by the rolling upgrade process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7628) Administration console - the cluster status doesn't reflect "reload-required" state of its nodes

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7628?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7628: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Administration console - the cluster status doesn't reflect "reload-required" state of its nodes > ------------------------------------------------------------------------------------------------ > > Key: ISPN-7628 > URL: https://issues.jboss.org/browse/ISPN-7628 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Final > > > The cluster has "Started" status even though all of its nodes have "reload-required" status. > Expected result: > The cluster status should also be "reload-required" > Another suggestion: > "Reload" action should be available from the cluster so that the user doesn't need to perform this action on individual nodes (there could be hundreds of them ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7644) Administration console - Loader tab allows invalid configuration to be set.

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7644: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Administration console - Loader tab allows invalid configuration to be set. > --------------------------------------------------------------------------- > > 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 > Fix For: 9.0.0.Final > > > 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-7637) Administration console - Store config change fails if wb is enabled, modal is opened and no value changed.

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7637?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7637: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Administration console - Store config change fails if wb is enabled, modal is opened and no value changed. > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-7637 > URL: https://issues.jboss.org/browse/ISPN-7637 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Ryan Emerson > Priority: Minor > Fix For: 9.0.0.Final > > > The issue is that when the user opens one of the pop-up dialogs in cache configuration (e.g. cache store -> Write behind), doesn't change anything and clicks OK, make some other changes, there is an error pop up when they try to save changes. > Steps to reproduce: > Set up a file store: > Cache container -> cache -> configuration -> Store tab -> Select file store -> apply -> ok -> restart later > Make a change: > - Cache container -> cache -> configuration -> Store tab > - change an attribute e.g. Read Only > - click on write behind (Don't change anything) -> click OK (WORKAROUND: if we click Cancel here instead of OK, everything works fine) > - apply changes -> confirm > result: > Error pop-up: > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-5":"WFLYCTL0201: Unknown attribute 'modified'"}} -- 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 Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7650?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7650. -------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.CR3) Resolution: Done > 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.CR4 > > > 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

[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: ---------------------------------------- For reference: I was unable to replicate same issue in master. It turns out that the "jboss-marshalling-osgi" package also contains the River classes. Even so, both master and 8.2.x end up shipping River marshaller 1.4.10 jars in its own module. The fact that master does not probably means that River marshaller 1.4.x module does not end up getting imported by the Infinispan Hot Rod layer, whereas in 8.2.x it somehow does and hence the River marshaller classes in "jboss-marshalling-osgi" module get mixed up. I didn't know but server/integration/bin directory contains some scripts to help with module dependencies. After talking to [~NadirX], he's agreed to take over since he's more knowledgeable on all this module business, because a question to ask is whether the River marshaller module jar could be ignored or trimmed, but having had a quick look to the module dependencies, seems like some Wildfly internals use it. > 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: Tristan Tarrant > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017