June 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4593) Expose a method to remove all instances of a type from the indexes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4593?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4593: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from VERIFIED to CLOSED > Expose a method to remove all instances of a type from the indexes > ------------------------------------------------------------------ > > Key: ISPN-4593 > URL: https://issues.jboss.org/browse/ISPN-4593 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > In Hibernate Search we have a method "purgeAll( type )", it seems Infinispan Query is missing this operation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3691) Make client side Connection refused error TRACE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3691?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3691: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1028411|https://bugzilla.redhat.com/show_bug.cgi?id=1028411] from VERIFIED to CLOSED > Make client side Connection refused error TRACE > ----------------------------------------------- > > Key: ISPN-3691 > URL: https://issues.jboss.org/browse/ISPN-3691 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.0.CR1, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 7.0.0.Final > > > After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused": > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE... > This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place. > Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one... > The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error. > Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4621) MassIndexer does not work on replicated cache (with local index)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4621?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4621: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from VERIFIED to CLOSED > MassIndexer does not work on replicated cache (with local index) > ---------------------------------------------------------------- > > Key: ISPN-4621 > URL: https://issues.jboss.org/browse/ISPN-4621 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha5 > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Priority: Critical > Fix For: 7.1.0.CR2 > > Attachments: ReplRamMassIndexingTest.java > > > MassIndexer indexes only entries that are primary on each node: other entries are missing when index is rebuilt. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-374) Add event handling to Hot Rod

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-374?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on ISPN-374: ---------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1186842|https://bugzilla.redhat.com/show_bug.cgi?id=1186842] from VERIFIED to CLOSED > Add event handling to Hot Rod > ----------------------------- > > Key: ISPN-374 > URL: https://issues.jboss.org/browse/ISPN-374 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: roadmap > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > Enable Hot Rod servers to send events asynchronously to registered clients over persistent connections. This would allow use cases such as clients maintaining L1 caches and these events could be used for servers to invalidate keys on the client side. See dev list thread for more info. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4971) CDI uses default EmbeddedCacheManager producer from infinispan-cdi.jar instead of custom one

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4971?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4971: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1163040|https://bugzilla.redhat.com/show_bug.cgi?id=1163040] from VERIFIED to CLOSED > CDI uses default EmbeddedCacheManager producer from infinispan-cdi.jar instead of custom one > -------------------------------------------------------------------------------------------- > > Key: ISPN-4971 > URL: https://issues.jboss.org/browse/ISPN-4971 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 7.0.0.CR1, 7.0.0.CR2, 7.0.0.Final > Reporter: Vitalii Chepeliuk > Assignee: Sebastian Łaskawiec > > Custom producer has allowDuplicateDomains set to true look following code > {code} > public class EmbeddedCacheManagerProducer { > /** > * Produces the default embedded cache manager. > * > * @param providedDefaultEmbeddedCacheManager the provided default embedded cache manager. > * @param defaultConfiguration the default configuration produced by the {@link EmbeddedCacheManagerProducer}. > * @return the default embedded cache manager used by the application. > */ > @Produces > @ApplicationScoped > public EmbeddedCacheManager getDefaultEmbeddedCacheManager(@OverrideDefault Instance<EmbeddedCacheManager> providedDefaultEmbeddedCacheManager, Configuration defaultConfiguration) { > GlobalConfiguration globalConfiguration = new GlobalConfigurationBuilder().globalJmxStatistics().allowDuplicateDomains(true).build(); > ConfigurationBuilder builder = new ConfigurationBuilder(); > builder.read(defaultConfiguration); > return new DefaultCacheManager(globalConfiguration, builder.build()); > } > /** > * Stops the default embedded cache manager when the corresponding instance is released. > * > * @param defaultEmbeddedCacheManager the default embedded cache manager. > */ > private void stopCacheManager(@Disposes EmbeddedCacheManager defaultEmbeddedCacheManager) { > defaultEmbeddedCacheManager.stop(); > } > } > {code} > And default ones from infinispan-cdi.jar is > {code} > public class DefaultEmbeddedCacheManagerProducer { > private static final Log log = LogFactory.getLog(DefaultEmbeddedCacheManagerProducer.class, Log.class); > /** > * Produces the default embedded cache manager. > * > * @param providedDefaultEmbeddedCacheManager the provided default embedded cache manager. > * @param defaultConfiguration the default configuration produced by the {@link DefaultEmbeddedCacheConfigurationProducer}. > * @return the default embedded cache manager used by the application. > */ > @Produces > @ApplicationScoped > @DefaultBean(EmbeddedCacheManager.class) > public EmbeddedCacheManager getDefaultEmbeddedCacheManager(@OverrideDefault Instance<EmbeddedCacheManager> providedDefaultEmbeddedCacheManager, Configuration defaultConfiguration) { > if (!providedDefaultEmbeddedCacheManager.isUnsatisfied()) { > log.tracef("Default embedded cache manager overridden by '%s'", providedDefaultEmbeddedCacheManager); > return providedDefaultEmbeddedCacheManager.get(); > } > return new DefaultCacheManager(defaultConfiguration); > } > /** > * Stops the default embedded cache manager when the corresponding instance is released. > * > * @param defaultEmbeddedCacheManager the default embedded cache manager. > */ > private void stopCacheManager(@Disposes EmbeddedCacheManager defaultEmbeddedCacheManager) { > defaultEmbeddedCacheManager.stop(); > } > } > {code} > When tests are deployed to APP server then following ERROR occurs > 10:19:58,494 ERROR [org.infinispan.jmx.JmxUtil] (http-localhost.localdomain/127.0.0.1:8080-1) ISPN000034: There's already an cache manager instance registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > 10:19:58,526 ERROR [org.infinispan.jmx.JmxUtil] (http-localhost.localdomain/127.0.0.1:8080-1) ISPN000034: There's already an cache manager instance registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > 10:19:58,598 ERROR [org.infinispan.jmx.JmxUtil] (http-localhost.localdomain/127.0.0.1:8080-1) ISPN000034: There's already an cache manager instance registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > What means that out custom producer is sometimes not used and does not override default produced EmbeddedCacheManager -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5087) CacheContainerStatsMBeanTest.testClusterStats() is failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5087?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5087: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1194355|https://bugzilla.redhat.com/show_bug.cgi?id=1194355] from VERIFIED to CLOSED > CacheContainerStatsMBeanTest.testClusterStats() is failing > ---------------------------------------------------------- > > Key: ISPN-5087 > URL: https://issues.jboss.org/browse/ISPN-5087 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Core > Affects Versions: 7.1.0.Alpha1 > Reporter: Pedro Ruivo > Assignee: Vladimir Blagojevic > Priority: Blocker > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > The test is always failing: > {code} > testClusterStats(org.infinispan.jmx.CacheContainerStatsMBeanTest) Time elapsed: 0.017 sec <<< FAILURE! > java.lang.AssertionError: expecting 0 for AverageWriteTime, to be greater than0 > at org.infinispan.jmx.CacheContainerStatsMBeanTest.assertAttributeValueGreaterThan(CacheContainerStatsMBeanTest.java:100) > at org.infinispan.jmx.CacheContainerStatsMBeanTest.testClusterStats(CacheContainerStatsMBeanTest.java:86) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5174) Transaction cannot be recommitted after ownership changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5174?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5174: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1207082|https://bugzilla.redhat.com/show_bug.cgi?id=1207082] from VERIFIED to CLOSED > Transaction cannot be recommitted after ownership changes > --------------------------------------------------------- > > Key: ISPN-5174 > URL: https://issues.jboss.org/browse/ISPN-5174 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.CR2, 7.1.1.Final > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > Once transaction is completed, it cannot commit again. If it should commit more keys since it has become an owner of some new keys modified in this transaction, it just ignores the further commit. > There is a race with state transfer which can bring an old value (with StateResponseCommand sent before it is commited) but the value is not set by the ongoing transaction either. > This results with stale value stored on one node. > In my case, The problematic part is transaction <edg-perf01-62141>:15066 (consisting of 10 modifications) which got prepared and committed on edg-perf04 in topology 25. Before the originator finishes, topology changes and 04 requests ongoing transactions: > {code} > 11:06:11,369 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (transport-thread-17) Replication task sending StateRequestCommand{cache=testCache, origin=edg-perf04-35097, type=GET_TRANSACTIONS, topologyId=28, segments=[275, 1, 278, 9, 282, 286, 17, 259, 25, 267, 171, 169, 33, 306, 175, 173, 310, 172, 314, 41, 167, 165, 318, 187, 290, 49, 185, 191, 294, 189, 179, 298, 57, 177, 183, 302, 181, 343, 205, 201, 338, 203, 336, 351, 197, 349, 199, 347, 193, 345, 195, 326, 85, 87, 322, 93, 332, 95, 330, 89, 91, 103, 101, 99, 506, 97, 105, 357, 359, 353, 355, 361]} to single recipient edg-perf01-62141 with response mode GET_ALL > 11:06:11,495 DEBUG [org.infinispan.statetransfer.StateConsumerImpl] (transport-thread-17) Applying 6 transactions for cache testCache transferred from node edg-perf01-62141 > {code} > However I don't see how these are applied, since PrepareCommand is not created again - from the code I see only that backup locks are added. Not sure if the transaction is registered at all, since it was already completed on this node (but at that time it did not own key_00000000000002EB). > After originator stores the entry, it sends one more CommitCommand with topology 28: > {code} > 11:06:11,619 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-2) Replication task sending CommitCommand {gtx=GlobalTransaction:<edg-perf01-62141>:15066:local, cacheName='testCache', topologyId=28} to addresses [edg-perf03-20530, edg-perf04-35097] with response mode GET_ALL > {code} > 04 receives several CommitCommands (both from originator and forwards), but all of them are ignored as the transaction is completed. > I don't see the logs where state transfer is assembled, but it's probably before the entry is stored on originator as the state transfer contains the old entry: > {code} > 11:06:13,449 TRACE [org.infinispan.statetransfer.StateConsumerImpl] (remote-thread-91) Received chunk with keys [key_000000000000065B, key_00000000000006BE, key_FFFFFFFFFFFFE62F, key_0000000000001F42, key_000000000000027B, key_000000000000159D, key_00000000000002EB, key_00000000000002BB] for segment 343 of cache testCache from node edg-perf01-62141 > 11:06:13,454 TRACE [org.infinispan.container.DefaultDataContainer] (remote-thread-91) Store ImmortalCacheEntry{key=key_00000000000002EB, value=[2 #7: 366, 544, 576, 804, 1061, 1181, 1290, ]} in container > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5501) Camel throwing java.lang.LinkageError for Remote Query when running in EAP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5501?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5501: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1213749|https://bugzilla.redhat.com/show_bug.cgi?id=1213749] from VERIFIED to CLOSED > Camel throwing java.lang.LinkageError for Remote Query when running in EAP > -------------------------------------------------------------------------- > > Key: ISPN-5501 > URL: https://issues.jboss.org/browse/ISPN-5501 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.2.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.2.Final, 8.0.0.Alpha1, 8.0.0.Final > > > The linkage error seems to be caused by the fact that some classes of package org.infinispan.query.dsl are present in two jars: infinispan-query-dsl.jar and infinispan-query.jar > The inclusion is a side-effect of this BND intruction dealing with split packages: https://github.com/infinispan/infinispan/blob/master/query/pom.xml#L143 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5019) After coordinator change, cache topologies should be installed in parallel

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5019?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5019: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1195565|https://bugzilla.redhat.com/show_bug.cgi?id=1195565] from VERIFIED to CLOSED > After coordinator change, cache topologies should be installed in parallel > -------------------------------------------------------------------------- > > Key: ISPN-5019 > URL: https://issues.jboss.org/browse/ISPN-5019 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.CR1, 7.2.0.Final > > > When the coordinator crashes, the new coordinator has to recover the cache topologies from all the nodes in the cluster and install updated topologies for all the caches. This is done on a single thread, and it can take a long time when there are a lot of caches. > We should be accelerate this by doing the topology installation on separate threads. However, we have to be careful with the async transport pool, because {{executeOnClusterAsync}} actually needs to spawn a new thread in the same pool. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5072) MapExternalizer no longer needs to extend InstanceReusingAdvancedExternalizer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5072?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5072: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1200525|https://bugzilla.redhat.com/show_bug.cgi?id=1200525] from VERIFIED to CLOSED > MapExternalizer no longer needs to extend InstanceReusingAdvancedExternalizer > ----------------------------------------------------------------------------- > > Key: ISPN-5072 > URL: https://issues.jboss.org/browse/ISPN-5072 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > The MapExternalizer originally extended InstanceReusingAdvancedExternalizer to allow for the CacheStatusResponse class to properly reuse values. However with ISPN-3561 we no longer use just a Map but also a ManagerStatusResponse so we only need the Externalizer for that class to extend InstanceReusingAdvancedExternalizer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2015