March 2016 - 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 days

2
1
0 / 0

[JBoss JIRA] (ISPN-6460) Race condition during server start causes wrong configuration to be used for cache 'default'

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6460: --------------------------------------- Summary: Race condition during server start causes wrong configuration to be used for cache 'default' Key: ISPN-6460 URL: https://issues.jboss.org/browse/ISPN-6460 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes The rest endpoint subsystem forces the startup of the "default" cache, whose configuration might not yet be read from the server xml and defined in the cache manager. As a result, the "default" cache will be started with a LOCAL configuration, and will never use the right configuration again. This can cause side effects such as the cache topology is not sent during a PingRequest (since cache is configured as LOCAL), also potentially ClearCommand failing with NPE since the default cache configuration is LOCAL in one node and clustered on another. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6459) NPE on cache.getCacheTopologyInfo

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6459?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6459: ------------------------------------ Steps to Reproduce: The error happen sometimes in this PR: https://github.com/infinispan/infinispan-hadoop/pull/6 when running on Travis. It's possible to reproduce locally by pinning the execution to a single CPU, running on a loop: {noformat} taskset -c 0 mvn clean install -Dtest=FailoverHandlingTest#testReadFromInfinispanSaveToHDFS_StopPreferedServer {noformat} was: The error happen sometimes in this PR: https://github.com/infinispan/infinispan-hadoop/pull/6 when running on Travis. It's possible to reproduce locally by pinning the execution to a single CPU, running on a loop {noformat} taskset -c 0 mvn clean install -Dtest=FailoverHandlingTest#testReadFromInfinispanSaveToHDFS_StopPreferedServer {noformat} > NPE on cache.getCacheTopologyInfo > --------------------------------- > > Key: ISPN-6459 > URL: https://issues.jboss.org/browse/ISPN-6459 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Sometimes {{cache.getTopologyInfo}} fails with: > {noformat} > java.lang.NullPointerException: null > at org.infinispan.client.hotrod.impl.CacheTopologyInfoImpl.getNumSegments(CacheTopologyInfoImpl.java:26) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6459) NPE on cache.getCacheTopologyInfo

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6459: --------------------------------------- Summary: NPE on cache.getCacheTopologyInfo Key: ISPN-6459 URL: https://issues.jboss.org/browse/ISPN-6459 Project: Infinispan Issue Type: Bug Components: Server Reporter: Gustavo Fernandes Sometimes {{cache.getTopologyInfo}} fails with: {noformat} java.lang.NullPointerException: null at org.infinispan.client.hotrod.impl.CacheTopologyInfoImpl.getNumSegments(CacheTopologyInfoImpl.java:26) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6459) NPE on cache.getCacheTopologyInfo

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6459?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-6459: --------------------------------------- Assignee: Gustavo Fernandes > NPE on cache.getCacheTopologyInfo > --------------------------------- > > Key: ISPN-6459 > URL: https://issues.jboss.org/browse/ISPN-6459 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Sometimes {{cache.getTopologyInfo}} fails with: > {noformat} > java.lang.NullPointerException: null > at org.infinispan.client.hotrod.impl.CacheTopologyInfoImpl.getNumSegments(CacheTopologyInfoImpl.java:26) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5557) Core threading redesign

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5557?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5557: ---------------------------------- Status: Open (was: New) > Core threading redesign > ----------------------- > > Key: ISPN-5557 > URL: https://issues.jboss.org/browse/ISPN-5557 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 9.0.0.Alpha1 > > > Infinispan needs a lot of threads, because everything is synchronous: locking, remote command invocations, cache writers. This causes various issues, from general context switching overhead to the thread pools getting full and causing deadlocks. > We should redesign the core so that most blocking happens on the application threads, and the number of internal threads is kept to a minimum. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1068) Add usage support similar to the one included in Spring Data

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1068?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-1068: ----------------------------------------- Assignee: Sebastian Łaskawiec (was: Gustavo Fernandes) > Add usage support similar to the one included in Spring Data > ------------------------------------------------------------ > > Key: ISPN-1068 > URL: https://issues.jboss.org/browse/ISPN-1068 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Marius Bogoevici > Assignee: Sebastian Łaskawiec > > ... i.e. InfinispanTemplate/InfinispanCallback -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6458) DistTopKeyTest.testLockLockFailed random failures

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6458?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6458: ------------------------------ Status: Open (was: New) > DistTopKeyTest.testLockLockFailed random failures > ------------------------------------------------- > > Key: ISPN-6458 > URL: https://issues.jboss.org/browse/ISPN-6458 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.Alpha1 > > > Random failures due to the async nature of the top key collection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6458) DistTopKeyTest.testLockLockFailed random failures

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6458?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6458: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4201 > DistTopKeyTest.testLockLockFailed random failures > ------------------------------------------------- > > Key: ISPN-6458 > URL: https://issues.jboss.org/browse/ISPN-6458 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.Alpha1 > > > Random failures due to the async nature of the top key collection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6424) Distributed Executor get can propagate exception if interrupt returns before cancellation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6424?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-6424 at 3/31/16 9:48 AM: ------------------------------------------------------------- You can use {{cache.getStatus().isStopping() || cache.getStatus().isTerminated()}} to see if the cache is shutting down. was (Author: dan.berindei): You can use `cache.getStatus().isStopping() || cache.getStatus().isTerminated()` to see if the cache is shutting down. > Distributed Executor get can propagate exception if interrupt returns before cancellation > ----------------------------------------------------------------------------------------- > > Key: ISPN-6424 > URL: https://issues.jboss.org/browse/ISPN-6424 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Alpha1 > > > This can cause get method to return an exception of the operation being interrupted instead of a CancellationException as it should. > This causes a test failure http://ci.infinispan.org/viewLog.html?buildId=37756&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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