January 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

2 weeks, 5 days

2
1
0 / 0

[JBoss JIRA] (ISPN-6090) Upgrade the metainf-services annotation processor to fix compilation issues on Java 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6090?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-6090: --------------------------------------- Nevermind, he released it right now: version {{1.7}} > Upgrade the metainf-services annotation processor to fix compilation issues on Java 9 > ------------------------------------------------------------------------------------- > > Key: ISPN-6090 > URL: https://issues.jboss.org/browse/ISPN-6090 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > When testing the build on JDK9, it currently fails because of https://java.net/jira/browse/METAINF_SERVICES-4 . > I reported the issue and provided a fix, let's upgrade the annotation processor once a release is out including the patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6090) Upgrade the metainf-services annotation processor to fix compilation issues on Java 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6090?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6090: ---------------------------------- Status: Open (was: New) > Upgrade the metainf-services annotation processor to fix compilation issues on Java 9 > ------------------------------------------------------------------------------------- > > Key: ISPN-6090 > URL: https://issues.jboss.org/browse/ISPN-6090 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Reporter: Sanne Grinovero > > When testing the build on JDK9, it currently fails because of https://java.net/jira/browse/METAINF_SERVICES-4 . > I reported the issue and provided a fix, let's upgrade the annotation processor once a release is out including the patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6090) Upgrade the metainf-services annotation processor to fix compilation issues on Java 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6090?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6090: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3970 > Upgrade the metainf-services annotation processor to fix compilation issues on Java 9 > ------------------------------------------------------------------------------------- > > Key: ISPN-6090 > URL: https://issues.jboss.org/browse/ISPN-6090 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Reporter: Sanne Grinovero > > When testing the build on JDK9, it currently fails because of https://java.net/jira/browse/METAINF_SERVICES-4 . > I reported the issue and provided a fix, let's upgrade the annotation processor once a release is out including the patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6090) Upgrade the metainf-services annotation processor to fix compilation issues on Java 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6090?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-6090: ------------------------------------- Assignee: Sanne Grinovero > Upgrade the metainf-services annotation processor to fix compilation issues on Java 9 > ------------------------------------------------------------------------------------- > > Key: ISPN-6090 > URL: https://issues.jboss.org/browse/ISPN-6090 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > When testing the build on JDK9, it currently fails because of https://java.net/jira/browse/METAINF_SERVICES-4 . > I reported the issue and provided a fix, let's upgrade the annotation processor once a release is out including the patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6090) Upgrade the metainf-services annotation processor to fix compilation issues on Java 9

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6090?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-6090: --------------------------------------- I met Kohsuke Kawaguchi at FOSDEM yesterday and he was so kind to look at my PR right away and merge it, he also published a snapshot. We could use a SNAPSHOT now? Or we'll have to wait for a release but I wonder how long that will be. > Upgrade the metainf-services annotation processor to fix compilation issues on Java 9 > ------------------------------------------------------------------------------------- > > Key: ISPN-6090 > URL: https://issues.jboss.org/browse/ISPN-6090 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Reporter: Sanne Grinovero > > When testing the build on JDK9, it currently fails because of https://java.net/jira/browse/METAINF_SERVICES-4 . > I reported the issue and provided a fix, let's upgrade the annotation processor once a release is out including the patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6127) Minor Stream Performance tweaks

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6127?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6127: -------------------------------- Status: Open (was: New) > Minor Stream Performance tweaks > ------------------------------- > > Key: ISPN-6127 > URL: https://issues.jboss.org/browse/ISPN-6127 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.1.0.Final > Reporter: William Burns > Fix For: 8.2.0.CR1 > > > We should remove usage of UUID to prevent entropy build up. Also generating a single integer is faster and has less payload. > Also there a few object allocations that can be prevented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6127) Minor Stream Performance tweaks

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6127?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6127: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3969 > Minor Stream Performance tweaks > ------------------------------- > > Key: ISPN-6127 > URL: https://issues.jboss.org/browse/ISPN-6127 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.1.0.Final > Reporter: William Burns > Fix For: 8.2.0.CR1 > > > We should remove usage of UUID to prevent entropy build up. Also generating a single integer is faster and has less payload. > Also there a few object allocations that can be prevented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3891: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Fix For: 8.2.0.CR1 > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3938) AdvancedAsyncCacheLoader.process() concurrency issues

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3938?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3938: ------------------------------- Fix Version/s: 8.2.0.CR1 (was: 8.2.0.Beta1) > AdvancedAsyncCacheLoader.process() concurrency issues > ----------------------------------------------------- > > Key: ISPN-3938 > URL: https://issues.jboss.org/browse/ISPN-3938 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > {{AdvancedAsyncCacheLoader.process()}} calls {{advancedLoader().process()}} to collect all the keys in the store, but the HashSet used to collect the keys it not thread-safe. This can cause problems, e.g. during state transfer: > {noformat} > WARN cheTopologyControlCommand | ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=sessions, type=CH_UPDATE, sender=alfie-lt-46127, joinInfo=null, topologyId=3, currentCH=DefaultConsistentHash{numSegments=60, numOwners=1, members=[alfie-lt-46127]}, pendingCH=null, throwable=null, viewId=1}java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926) > at java.util.HashMap$KeyIterator.next(HashMap.java:960) > at org.infinispan.persistence.async.AdvancedAsyncCacheLoader.process(AdvancedAsyncCacheLoader.java:80) > at org.infinispan.persistence.manager.PersistenceManagerImpl.processOnAllStores(PersistenceManagerImpl.java:414) > at org.infinispan.statetransfer.StateConsumerImpl.invalidateSegments(StateConsumerImpl.java:910) > at org.infinispan.statetransfer.StateConsumerImpl.onTopologyUpdate(StateConsumerImpl.java:393) > at org.infinispan.statetransfer.StateTransferManagerImpl.doTopologyUpdate(StateTransferManagerImpl.java:178) > at org.infinispan.statetransfer.StateTransferManagerImpl.access$000(StateTransferManagerImpl.java:38) > at org.infinispan.statetransfer.StateTransferManagerImpl$1.updateConsistentHash(StateTransferManagerImpl.java:100) > at org.infinispan.topology.LocalTopologyManagerImpl.handleConsistentHashUpdate(LocalTopologyManagerImpl.java:191) > at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:152) > at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:124) > at org.infinispan.topology.ClusterTopologyManagerImpl$3.run(ClusterTopologyManagerImpl.java:606) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016