May 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7144) Cross-Site Replication: inconsistent data with multiple site masters

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7144?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7144: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.1.0.Alpha1 Resolution: Done > Cross-Site Replication: inconsistent data with multiple site masters > -------------------------------------------------------------------- > > Key: ISPN-7144 > URL: https://issues.jboss.org/browse/ISPN-7144 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 9.0.0.Alpha4 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.1.Final, 9.1.0.Alpha1 > > > Cross-Site replication with multiple site masters may not work properly when configured asynchronously. > It relies on the deliver order of the updates to the remote site but, with multiple site masters, it is possible an update to go through one of the possible routes. Having commands going through different routes violates the FIFO order needed leading to inconsistent data between sites. > Note: it doesn't happen in synchronous mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5655) MissingFormatArgumentException thrown by PreferConsistencyStrategy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5655?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5655: ----------------------------------------------- Jakub Senko <jsenko(a)redhat.com> changed the Status of [bug 1412752|https://bugzilla.redhat.com/show_bug.cgi?id=1412752] from MODIFIED to ON_QA > MissingFormatArgumentException thrown by PreferConsistencyStrategy > ------------------------------------------------------------------ > > Key: ISPN-5655 > URL: https://issues.jboss.org/browse/ISPN-5655 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 8.0.0.Beta3, 8.0.0.Final > > > Exception thrown due to line 197 in PreferConsistencyStrategy.java > 2015-08-03 10:30:38,873 ERROR Unable to format msg: After merge, cache %s has recovered and is entering available mode java.util.MissingFormatArgumentException: Format specifier '%s' > at java.util.Formatter.format(Formatter.java:2519) > at java.util.Formatter.format(Formatter.java:2455) > at java.lang.String.format(String.java:2928) > at org.apache.logging.log4j.message.StringFormattedMessage.formatMessage(StringFormattedMessage.java:88) > at org.apache.logging.log4j.message.StringFormattedMessage.getFormattedMessage(StringFormattedMessage.java:60) > at org.apache.logging.log4j.core.pattern.MessagePatternConverter.format(MessagePatternConverter.java:68) > at org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:36) > at org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:196) > at org.apache.logging.log4j.core.layout.PatternLayout.toSerializable(PatternLayout.java:55) > at org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:71) > at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:108) > at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:99) > at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:430) > at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:409) > at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:412) > at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:367) > at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:112) > at org.jboss.logging.Log4j2Logger.doLogf(Log4j2Logger.java:66) > at org.jboss.logging.Logger.logf(Logger.java:2445) > at org.jboss.logging.DelegatingBasicLogger.debugf(DelegatingBasicLogger.java:344) > at org.infinispan.partitionhandling.impl.PreferConsistencyStrategy.onPartitionMerge(PreferConsistencyStrategy.java:198) > at org.infinispan.topology.ClusterCacheStatus.doMergePartitions(ClusterCacheStatus.java:509) > at org.infinispan.topology.ClusterTopologyManagerImpl$2.call(ClusterTopologyManagerImpl.java:383) > at org.infinispan.topology.ClusterTopologyManagerImpl$2.call(ClusterTopologyManagerImpl.java:380) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7850) JDBC Migrator 9.x Marshaller Incorrectly Loaded

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7850?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7850: ------------------------------- Status: Open (was: New) > JDBC Migrator 9.x Marshaller Incorrectly Loaded > ----------------------------------------------- > > Key: ISPN-7850 > URL: https://issues.jboss.org/browse/ISPN-7850 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.1.Final, 9.1.0.Alpha1 > > > When loading the CURRENT marshaller we extract it from an existing CacheManager and place it in the config for the target cache manager. This is wrong, because it results in the GlobalMarshaller having another instance of a GlobalMarshaller as the `external` marshaller, resulting in an infinite loop occurring when attempting to extract externalizers from the SerializeWith annotation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7850) JDBC Migrator 9.x Marshaller Incorrectly Loaded

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7850?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7850: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5142 > JDBC Migrator 9.x Marshaller Incorrectly Loaded > ----------------------------------------------- > > Key: ISPN-7850 > URL: https://issues.jboss.org/browse/ISPN-7850 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.1.Final, 9.1.0.Alpha1 > > > When loading the CURRENT marshaller we extract it from an existing CacheManager and place it in the config for the target cache manager. This is wrong, because it results in the GlobalMarshaller having another instance of a GlobalMarshaller as the `external` marshaller, resulting in an infinite loop occurring when attempting to extract externalizers from the SerializeWith annotation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7850) JDBC Migrator 9.x Marshaller Incorrectly Loaded

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-7850: ---------------------------------- Summary: JDBC Migrator 9.x Marshaller Incorrectly Loaded Key: ISPN-7850 URL: https://issues.jboss.org/browse/ISPN-7850 Project: Infinispan Issue Type: Bug Affects Versions: 9.0.0.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.0.1.Final, 9.1.0.Alpha1 When loading the CURRENT marshaller we extract it from an existing CacheManager and place it in the config for the target cache manager. This is wrong, because it results in the GlobalMarshaller having another instance of a GlobalMarshaller as the `external` marshaller, resulting in an infinite loop occurring when attempting to extract externalizers from the SerializeWith annotation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6539) ClassCastException with Remote Cache Loader and GetWithMetadata

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6539?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-6539: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1435617|https://bugzilla.redhat.com/show_bug.cgi?id=1435617] from ON_QA to VERIFIED > ClassCastException with Remote Cache Loader and GetWithMetadata > --------------------------------------------------------------- > > Key: ISPN-6539 > URL: https://issues.jboss.org/browse/ISPN-6539 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores, Server > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > A combination of remote cache loader and {{IsolationLevel.REPEATABLE_READ}} will cause a ClassCastException when doing a {{GetWithMetadata}}: > {noformat} > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=11 > returned server error (status=0x85): java.lang.ClassCastException: > org.infinispan.container.entries.RepeatableReadEntry cannot be cast to > org.infinispan.container.entries.InternalCacheEntry > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7578) EntryWrappingInterceptor should not invoke tx commands synchronously

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7578?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7578: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.1.0.Alpha1 Resolution: Done > EntryWrappingInterceptor should not invoke tx commands synchronously > -------------------------------------------------------------------- > > Key: ISPN-7578 > URL: https://issues.jboss.org/browse/ISPN-7578 > Project: Infinispan > Issue Type: Bug > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.1.0.Alpha1 > > > {{EntryWrappingInterceptor.wrapEntriesForPrepare}} invokes sub-commands synchronously, as we expect that these will be non-blocking. However if the sub-command needs to fetch remote value (as ReadWrite* commands or PutKeyValueCommand with DELTA_WRITE does), we block the thread in the meantime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7847) Deprecate DeltaAware and ApplyDeltaCommand

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7847?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7847: ------------------------------ Status: Open (was: New) > Deprecate DeltaAware and ApplyDeltaCommand > ------------------------------------------ > > Key: ISPN-7847 > URL: https://issues.jboss.org/browse/ISPN-7847 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.1.0.Final > > > After ISPN-7803 gets in {{DeltaAware}} should be deprecated and any current use replaced with functional commands. > {{Cache.applyDelta}} will be deprecated, too, implementation replaced by a functional call/{{compute}}. > {{ApplyDeltaCommand}} should be deprecated, any implementation of {{visitApplyDeltaCommand}} in interceptor stack removed. > {{DeltaAwareCacheEntry}} and all its uses will be removed immediately. > {{Flag.DELTA_WRITE}} will be deprecated and all its uses removed. > We can't really test if the semantics is preserved since it's broken by design, but let's at least make sure that we don't break {{infinispan-lucene-directory}} (which should be migrated later on). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7849) Uber jars have lots of compile-time dependencies

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7849: ----------------------------------------- Summary: Uber jars have lots of compile-time dependencies Key: ISPN-7849 URL: https://issues.jboss.org/browse/ISPN-7849 Project: Infinispan Issue Type: Bug Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Priority: Critical Just have a look at dependencies section in Maven Central: https://mvnrepository.com/artifact/org.infinispan/infinispan-embedded/9.0... The Uber Jar should not provide any of those! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7767) Decide whether to use, or not to use Optionals

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7767?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec closed ISPN-7767. ------------------------------------- Resolution: Done > Decide whether to use, or not to use Optionals > ---------------------------------------------- > > Key: ISPN-7767 > URL: https://issues.jboss.org/browse/ISPN-7767 > Project: Infinispan > Issue Type: Sub-task > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017