January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11084) Log an ERROR if golbal state is not enabled whenever internal caches with Flag.PERSISTENT are created

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11084?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11084: -------------------------------- Fix Version/s: 9.4.18.Final > Log an ERROR if golbal state is not enabled whenever internal caches with Flag.PERSISTENT are created > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-11084 > URL: https://issues.redhat.com/browse/ISPN-11084 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Reporter: Nistor Adrian > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final, 9.4.18.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11175) Improve Log::unsupportedConfiguration method adding that a missing dependency can cause the issue

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11175?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11175: ----------------------------------- Fix Version/s: 9.4.18.Final > Improve Log::unsupportedConfiguration method adding that a missing dependency can cause the issue > ------------------------------------------------------------------------------------------------- > > Key: ISPN-11175 > URL: https://issues.redhat.com/browse/ISPN-11175 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.0.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > Fix For: 10.1.1.Final, 9.4.18.Final > > > The config file {{string-based.xml}} is not working > {code:java} > new DefaultCacheManager("/path/to/persistence/jdbc/src/test/resources/configs/string-based.xml") > {code} > {noformat} > org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace ''. Check that your configuration is up-to date for this version of Infinispan. > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:174) > at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:38) > at org.infinispan.configuration.parsing.Parser.parsePersistence(Parser.java:2361) > at org.infinispan.configuration.parsing.Parser.parseCacheElement(Parser.java:1544) > at org.infinispan.configuration.parsing.Parser.parseLocalCache(Parser.java:1248) > at org.infinispan.configuration.parsing.Parser.parseContainer(Parser.java:579) > at org.infinispan.configuration.parsing.Parser.readElement(Parser.java:116) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11175) Improve Log::unsupportedConfiguration method adding that a missing dependency can cause the issue

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11175?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11175: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.1.Final Resolution: Done > Improve Log::unsupportedConfiguration method adding that a missing dependency can cause the issue > ------------------------------------------------------------------------------------------------- > > Key: ISPN-11175 > URL: https://issues.redhat.com/browse/ISPN-11175 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.0.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > Fix For: 10.1.1.Final > > > The config file {{string-based.xml}} is not working > {code:java} > new DefaultCacheManager("/path/to/persistence/jdbc/src/test/resources/configs/string-based.xml") > {code} > {noformat} > org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace ''. Check that your configuration is up-to date for this version of Infinispan. > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:174) > at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:38) > at org.infinispan.configuration.parsing.Parser.parsePersistence(Parser.java:2361) > at org.infinispan.configuration.parsing.Parser.parseCacheElement(Parser.java:1544) > at org.infinispan.configuration.parsing.Parser.parseLocalCache(Parser.java:1248) > at org.infinispan.configuration.parsing.Parser.parseContainer(Parser.java:579) > at org.infinispan.configuration.parsing.Parser.readElement(Parser.java:116) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6375) Metaspace memory leak with infinispan

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-6375?page=com.atlassian.jira.plugin... ] Dan Berindei resolved ISPN-6375. -------------------------------- Fix Version/s: 9.0.0.Final Resolution: Out of Date Fixed when we removed {{EquivalentConcurrentHashMapV8}} and replaced it with Caffeine. > Metaspace memory leak with infinispan > ------------------------------------- > > Key: ISPN-6375 > URL: https://issues.redhat.com/browse/ISPN-6375 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.1.2.Final > Reporter: Andrej Dmitrenko > Priority: Major > Fix For: 9.0.0.Final > > Attachments: memory-analyzer.png > > > I use infinispan for embedded cache and criteria query in cache. It is works great! > I start infinispan in my application and call embeddedCacheManager.stop() at application destroy. > I run my application in oracle weblogic 12.1.3 server. And after redeploy my application I see metaspace memory leak. > I have checked heap dump in memory analizer. > The cause in thread local variable threadCounterHashCode in org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$CounterHashCode class > After undeploy aplication there is a thread which keep thread local reference to threadCounterHashCode, and threadCounterHashCode keep link to classloader and that's why classloader cannot be removed from metaspace memory. > I cannot control this thread. > I have got suggestion in forum to create ticket in JIRA (https://developer.jboss.org/message/952848) > Please do something with class org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$CounterHashCode to avoid metaspace memory leak in cases when user does not control thread pool -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11164) Docs: Clustered max idle updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11164?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11164: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7742, https://github.com/infinispan/infinispan/pull/7751 (was: https://github.com/infinispan/infinispan/pull/7742) > Docs: Clustered max idle updates > -------------------------------- > > Key: ISPN-11164 > URL: https://issues.redhat.com/browse/ISPN-11164 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.1.Final, 11.0.0.Final > > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11164) Docs: Clustered max idle updates

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11164?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11164: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.1.Final 11.0.0.Final Resolution: Done > Docs: Clustered max idle updates > -------------------------------- > > Key: ISPN-11164 > URL: https://issues.redhat.com/browse/ISPN-11164 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.1.Final, 11.0.0.Final > > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11177) Automatically set jboss.modules.settings.xml.url to the root maven-settings.xml file

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11177?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11177: ----------------------------------- Status: Open (was: New) > Automatically set jboss.modules.settings.xml.url to the root maven-settings.xml file > ------------------------------------------------------------------------------------ > > Key: ISPN-11177 > URL: https://issues.redhat.com/browse/ISPN-11177 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.1.Final > > > The build requires setting `jboss.modules.settings.xml.url` to point to the maven settings file to use. Since the maven-settings.xml in the root of the project points to the correct environment, we can default to that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11177) Automatically set jboss.modules.settings.xml.url to the root maven-settings.xml file

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11177?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11177: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7750 > Automatically set jboss.modules.settings.xml.url to the root maven-settings.xml file > ------------------------------------------------------------------------------------ > > Key: ISPN-11177 > URL: https://issues.redhat.com/browse/ISPN-11177 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.1.Final > > > The build requires setting `jboss.modules.settings.xml.url` to point to the maven settings file to use. Since the maven-settings.xml in the root of the project points to the correct environment, we can default to that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11177) Automatically set jboss.modules.settings.xml.url to the root maven-settings.xml file

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11177: -------------------------------------- Summary: Automatically set jboss.modules.settings.xml.url to the root maven-settings.xml file Key: ISPN-11177 URL: https://issues.redhat.com/browse/ISPN-11177 Project: Infinispan Issue Type: Enhancement Components: Build Affects Versions: 10.1.0.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.1.1.Final The build requires setting `jboss.modules.settings.xml.url` to point to the maven settings file to use. Since the maven-settings.xml in the root of the project points to the correct environment, we can default to that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11175) Improve Log::unsupportedConfiguration method adding that a missing dependency can cause the issue

by Alan Field (Jira)

[ https://issues.redhat.com/browse/ISPN-11175?page=com.atlassian.jira.plugi... ] Alan Field updated ISPN-11175: ------------------------------ Description: The config file {{string-based.xml}} is not working {code:java} new DefaultCacheManager("/path/to/persistence/jdbc/src/test/resources/configs/string-based.xml") {code} {noformat} org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace ''. Check that your configuration is up-to date for this version of Infinispan. at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:174) at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:38) at org.infinispan.configuration.parsing.Parser.parsePersistence(Parser.java:2361) at org.infinispan.configuration.parsing.Parser.parseCacheElement(Parser.java:1544) at org.infinispan.configuration.parsing.Parser.parseLocalCache(Parser.java:1248) at org.infinispan.configuration.parsing.Parser.parseContainer(Parser.java:579) at org.infinispan.configuration.parsing.Parser.readElement(Parser.java:116) {noformat} was: The config file {{string-based.xml}} is not working {code:java} new DefaultCacheManager("/path/to/persistence/jdbc/src/test/resources/configs/string-based.xml) {code} {noformat} org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace ''. Check that your configuration is up-to date for this version of Infinispan. at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:174) at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:38) at org.infinispan.configuration.parsing.Parser.parsePersistence(Parser.java:2361) at org.infinispan.configuration.parsing.Parser.parseCacheElement(Parser.java:1544) at org.infinispan.configuration.parsing.Parser.parseLocalCache(Parser.java:1248) at org.infinispan.configuration.parsing.Parser.parseContainer(Parser.java:579) at org.infinispan.configuration.parsing.Parser.readElement(Parser.java:116) {noformat} > Improve Log::unsupportedConfiguration method adding that a missing dependency can cause the issue > ------------------------------------------------------------------------------------------------- > > Key: ISPN-11175 > URL: https://issues.redhat.com/browse/ISPN-11175 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.0.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > > The config file {{string-based.xml}} is not working > {code:java} > new DefaultCacheManager("/path/to/persistence/jdbc/src/test/resources/configs/string-based.xml") > {code} > {noformat} > org.infinispan.commons.CacheConfigurationException: ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace ''. Check that your configuration is up-to date for this version of Infinispan. > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:174) > at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:38) > at org.infinispan.configuration.parsing.Parser.parsePersistence(Parser.java:2361) > at org.infinispan.configuration.parsing.Parser.parseCacheElement(Parser.java:1544) > at org.infinispan.configuration.parsing.Parser.parseLocalCache(Parser.java:1248) > at org.infinispan.configuration.parsing.Parser.parseContainer(Parser.java:579) > at org.infinispan.configuration.parsing.Parser.readElement(Parser.java:116) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020