March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2575: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > KeyTransformer registration is required on all nodes of the cluster, in case of custom keys > ------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

1 week

2
1
0 / 0

[JBoss JIRA] (ISPN-10095) Shared stores should throw exception when cache is local

by Vladimir Dzhuvinov (Jira)

[ https://issues.jboss.org/browse/ISPN-10095?page=com.atlassian.jira.plugin... ] Vladimir Dzhuvinov commented on ISPN-10095: ------------------------------------------- Yesterday we encountered this issue in a test with local cache and shared=true, the test ran but an NPE exception was noticed in the logs: {{2019-03-30T02:25:42,016 WARN expiration-thread--p3-t1 PersistenceManagerImpl - ISPN000026: Caught exception purging data container! java.lang.NullPointerException: null at org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$purgeExpired$6(PersistenceManagerImpl.java:454) ~[infinispan-core-9.4.11.Final.jar:9.4.11.Final] at java.util.ArrayList.forEach(ArrayList.java:1257) ~[?:1.8.0_191] at org.infinispan.persistence.manager.PersistenceManagerImpl.purgeExpired(PersistenceManagerImpl.java:465) [infinispan-core-9.4.11.Final.jar:9.4.11.Final] at org.infinispan.expiration.impl.ExpirationManagerImpl.processExpiration(ExpirationManagerImpl.java:111) [infinispan-core-9.4.11.Final.jar:9.4.11.Final] at org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:245) [infinispan-core-9.4.11.Final.jar:9.4.11.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_191] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_191] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_191] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]}} > Shared stores should throw exception when cache is local > -------------------------------------------------------- > > Key: ISPN-10095 > URL: https://issues.jboss.org/browse/ISPN-10095 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 10.0.0.Beta3, 9.4.11.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > A shared store does not make sense with a local cache, therefore we should throw a {{CacheConfigurationException}} if configured. Due to assumptions elsewhere in the PersistenceManager, prior to this fix a NPE will be thrown during the Purge method of the store as {{transport == null}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7146) Expiration interval set to -1 doesn't disable the expiration thread

by Vladimir Dzhuvinov (Jira)

[ https://issues.jboss.org/browse/ISPN-7146?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov updated ISPN-7146: ------------------------------------- Summary: Expiration interval set to -1 doesn't disable the expiration thread (was: Expiration interval set to -1 behaves incorrectly) > Expiration interval set to -1 doesn't disable the expiration thread > ------------------------------------------------------------------- > > Key: ISPN-7146 > URL: https://issues.jboss.org/browse/ISPN-7146 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Will Burns > Priority: Major > > According to the guide and XML docs <expiration interval="-1"/> disables the expiration thread. But it doesn't, and expiration proceeds to run every 1 minute (which is the default behaviour when the expiration setting is omitted). > Later I found that it takes <expiration interval="0"/> to disable the expiration thread. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7146) Expiration interval set to -1 behaves incorrectly

by Vladimir Dzhuvinov (Jira)

[ https://issues.jboss.org/browse/ISPN-7146?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov edited comment on ISPN-7146 at 3/30/19 3:35 AM: ------------------------------------------------------------------- The issue is still present in 9.4.11.Final. According to the config schema docs and JavaDocs -1 is still given as the value to disable the thread: _interval long 60000 Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set interval to -1._ When checking the XML config for `interval="-1"` programmatically Infinispan returns 60000: {{Configuration.expiration().wakeUpInterval()}} was (Author: vdzhuvinov): The issue is still present in 9.4.11.Final. According to the config schema docs and JavaDocs -1 is still given as the value to disable the thread: _interval long 60000 Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set interval to -1._ > Expiration interval set to -1 behaves incorrectly > ------------------------------------------------- > > Key: ISPN-7146 > URL: https://issues.jboss.org/browse/ISPN-7146 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Will Burns > Priority: Major > > According to the guide and XML docs <expiration interval="-1"/> disables the expiration thread. But it doesn't, and expiration proceeds to run every 1 minute (which is the default behaviour when the expiration setting is omitted). > Later I found that it takes <expiration interval="0"/> to disable the expiration thread. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7146) Expiration interval set to -1 behaves incorrectly

by Vladimir Dzhuvinov (Jira)

[ https://issues.jboss.org/browse/ISPN-7146?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov updated ISPN-7146: ------------------------------------- Priority: Major (was: Minor) > Expiration interval set to -1 behaves incorrectly > ------------------------------------------------- > > Key: ISPN-7146 > URL: https://issues.jboss.org/browse/ISPN-7146 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Will Burns > Priority: Major > > According to the guide and XML docs <expiration interval="-1"/> disables the expiration thread. But it doesn't, and expiration proceeds to run every 1 minute (which is the default behaviour when the expiration setting is omitted). > Later I found that it takes <expiration interval="0"/> to disable the expiration thread. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7146) Expiration interval set to -1 behaves incorrectly

by Vladimir Dzhuvinov (Jira)

[ https://issues.jboss.org/browse/ISPN-7146?page=com.atlassian.jira.plugin.... ] Vladimir Dzhuvinov commented on ISPN-7146: ------------------------------------------ The issue is still present in 9.4.11.Final. According to the config schema docs and JavaDocs -1 is still given as the value to disable the thread: _interval long 60000 Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set interval to -1._ > Expiration interval set to -1 behaves incorrectly > ------------------------------------------------- > > Key: ISPN-7146 > URL: https://issues.jboss.org/browse/ISPN-7146 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Will Burns > Priority: Minor > > According to the guide and XML docs <expiration interval="-1"/> disables the expiration thread. But it doesn't, and expiration proceeds to run every 1 minute (which is the default behaviour when the expiration setting is omitted). > Later I found that it takes <expiration interval="0"/> to disable the expiration thread. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10098) Remove misc deprecated server code

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10098?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10098: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6821 > Remove misc deprecated server code > ---------------------------------- > > Key: ISPN-10098 > URL: https://issues.jboss.org/browse/ISPN-10098 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > There are many examples in the server code of dangling ModelKeys, attributes etc that have been deprecated but not removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10098) Remove misc deprecated server code

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10098?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10098: -------------------------------- Status: Open (was: New) > Remove misc deprecated server code > ---------------------------------- > > Key: ISPN-10098 > URL: https://issues.jboss.org/browse/ISPN-10098 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > There are many examples in the server code of dangling ModelKeys, attributes etc that have been deprecated but not removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10097) Remove unused "start" attribute from server config

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10097?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10097: -------------------------------- Sprint: (was: JDG Sprint #27) > Remove unused "start" attribute from server config > -------------------------------------------------- > > Key: ISPN-10097 > URL: https://issues.jboss.org/browse/ISPN-10097 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > The start="EAGER|LAZY" attribute is never used, we should remove this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10097) Remove unused "start" attribute from server config

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10097?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10097: -------------------------------- Sprint: JDG Sprint #27 > Remove unused "start" attribute from server config > -------------------------------------------------- > > Key: ISPN-10097 > URL: https://issues.jboss.org/browse/ISPN-10097 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > The start="EAGER|LAZY" attribute is never used, we should remove this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019