January 2021 - infinispan-issues - Jboss List Archives

[Red Hat JIRA] (ISPN-12654) Get entry broken in protobuf caches

by Katia Aresti (Jira)

Katia Aresti created ISPN-12654: ----------------------------------- Summary: Get entry broken in protobuf caches Key: ISPN-12654 URL: https://issues.redhat.com/browse/ISPN-12654 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 12.0.0.Final Reporter: Katia Aresti Assignee: Katia Aresti When we find a key and the key is a protobuf value, we don't get the key _value, so there is a json parser error for that case -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12635) Multimap Bucket can't get replicated in server mode

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12635?page=com.atlassian.jira.plugi... ] Pedro Ruivo commented on ISPN-12635: ------------------------------------ Test fix here: https://github.com/infinispan/infinispan/pull/9009 > Multimap Bucket can't get replicated in server mode > --------------------------------------------------- > > Key: ISPN-12635 > URL: https://issues.redhat.com/browse/ISPN-12635 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 12.0.0.CR1 > Reporter: Katia Aresti > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 12.0.0.Final, 12.1.0.Final > > > Mulitmap put/get only sends the function over the network, which works fine. But, if you have to replicate the {{Bucket}} class, it will fail (state transfer & cross-site are 2 examples) > This happens because of {{MultimapRequestProcessor}} which wraps the user's key & value with {{WrappedByteArray}} and the "user marhsaller" is unable to handle {{WrappedByteArray}}. Wrapping the keys & values with {{WrappedByteArray}} is no longer necessary and it should be removed. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12635) Multimap Bucket can't get replicated in server mode

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12635?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12635: ------------------------------- Fix Version/s: 12.1.0.Final > Multimap Bucket can't get replicated in server mode > --------------------------------------------------- > > Key: ISPN-12635 > URL: https://issues.redhat.com/browse/ISPN-12635 > Project: Infinispan > Issue Type: Bug > Components: Multimap > Affects Versions: 12.0.0.CR1 > Reporter: Katia Aresti > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 12.0.0.Final, 12.1.0.Final > > > Mulitmap put/get only sends the function over the network, which works fine. But, if you have to replicate the {{Bucket}} class, it will fail (state transfer & cross-site are 2 examples) > This happens because of {{MultimapRequestProcessor}} which wraps the user's key & value with {{WrappedByteArray}} and the "user marhsaller" is unable to handle {{WrappedByteArray}}. Wrapping the keys & values with {{WrappedByteArray}} is no longer necessary and it should be removed. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12622) Expose Cross-Site Views via CLI and REST endpoint

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12622?page=com.atlassian.jira.plugi... ] Pedro Ruivo commented on ISPN-12622: ------------------------------------ I've added the xsite view to the cache manager info: https://github.com/infinispan/infinispan/pull/9008/files#diff-98f2f132a83... > Expose Cross-Site Views via CLI and REST endpoint > ------------------------------------------------- > > Key: ISPN-12622 > URL: https://issues.redhat.com/browse/ISPN-12622 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, Cross-Site Replication, REST > Affects Versions: 12.0.0.CR1 > Reporter: Dmitry Volodin > Assignee: Pedro Ruivo > Priority: Major > > {color:#333333}Now Cross-Site View prints message `{color:#000000}Check log messages for ISPN000439: Received new x-site view messages.` {color}inside log or this status can be obtained via JMX only. > {color} > {color:#333333}For issue [https://github.com/infinispan/infinispan-operator/issues/193] implementation it would be nice to have a REST endpoint to get this info > {color} -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12622) Expose Cross-Site Views via CLI and REST endpoint

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12622?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12622: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/9008 Status: Pull Request Sent (was: Coding In Progress) > Expose Cross-Site Views via CLI and REST endpoint > ------------------------------------------------- > > Key: ISPN-12622 > URL: https://issues.redhat.com/browse/ISPN-12622 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, Cross-Site Replication, REST > Affects Versions: 12.0.0.CR1 > Reporter: Dmitry Volodin > Assignee: Pedro Ruivo > Priority: Major > > {color:#333333}Now Cross-Site View prints message `{color:#000000}Check log messages for ISPN000439: Received new x-site view messages.` {color}inside log or this status can be obtained via JMX only. > {color} > {color:#333333}For issue [https://github.com/infinispan/infinispan-operator/issues/193] implementation it would be nice to have a REST endpoint to get this info > {color} -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12622) Expose Cross-Site Views via CLI and REST endpoint

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12622?page=com.atlassian.jira.plugi... ] Work on ISPN-12622 started by Pedro Ruivo. ------------------------------------------ > Expose Cross-Site Views via CLI and REST endpoint > ------------------------------------------------- > > Key: ISPN-12622 > URL: https://issues.redhat.com/browse/ISPN-12622 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, Cross-Site Replication, REST > Affects Versions: 12.0.0.CR1 > Reporter: Dmitry Volodin > Assignee: Pedro Ruivo > Priority: Major > > {color:#333333}Now Cross-Site View prints message `{color:#000000}Check log messages for ISPN000439: Received new x-site view messages.` {color}inside log or this status can be obtained via JMX only. > {color} > {color:#333333}For issue [https://github.com/infinispan/infinispan-operator/issues/193] implementation it would be nice to have a REST endpoint to get this info > {color} -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-11180) Make Spring Integration work with Protostream marshaller

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11180?page=com.atlassian.jira.plugi... ] Dan Berindei closed ISPN-11180. ------------------------------- Resolution: Duplicate Issue Duplicate of ISPN-12268 > Make Spring Integration work with Protostream marshaller > -------------------------------------------------------- > > Key: ISPN-11180 > URL: https://issues.redhat.com/browse/ISPN-11180 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Affects Versions: 10.1.0.Final > Reporter: Katia Aresti > Priority: Critical > > Today Spring integration won't work with Protostream. We need to change several things to make this work: > - MapSession object that is used from the Spring Session integration > - NullValue object should be marshallable by protostream -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12653) Duplicate classes in infinispan-spring5-embedded and infinispan-spring5-common

by Kai Lehmann (Jira)

Kai Lehmann created ISPN-12653: ---------------------------------- Summary: Duplicate classes in infinispan-spring5-embedded and infinispan-spring5-common Key: ISPN-12653 URL: https://issues.redhat.com/browse/ISPN-12653 Project: Infinispan Issue Type: Bug Affects Versions: 11.0.9.Final Reporter: Kai Lehmann infinispan-spring5-common and infinispan-spring5-embedded (at least in version 11.0.9 Final) have the following duplicate classes: {noformat} org/infinispan/spring/common/session/AbstractInfinispanSessionRepository.class org/infinispan/spring/common/config/InfinispanNamespaceHandler.class org/infinispan/spring/common/session/AbstractApplicationPublisherBridge.class org/infinispan/spring/common/session/PrincipalNameResolver.class org/infinispan/spring/common/provider/NullValue.class org/infinispan/spring/common/provider/SpringCache$ValueRetrievalExceptionResolver.class org/infinispan/spring/common/provider/SpringCache.class org/infinispan/spring/common/config/InfinispanContainerCacheManagerBeanDefinitionParser.class org/infinispan/spring/common/config/InfinispanRemoteCacheManagerBeanDefinitionParser.class org/infinispan/spring/common/config/InfinispanEmbeddedCacheManagerBeanDefinitionParser.class org/infinispan/spring/common/config/InfinispanNamespaceUtils.class {noformat} Our infrastructure checks for duplicate classes in different components within the dependency tree and is complaing about this. Duplicate classes is usually a bad thing. It is not deterministic which one will survive when merged into a jar/war file which can lead to unexpected behavior at runtime. I guess those class contents are the same here, but nevertheless the duplicates should be removed. As embedded is depending on commons, I think it should be safe to remove those classes from embedded. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12652) Cluster is broken after one node is down

by Dmitry Kruglikov (Jira)

Dmitry Kruglikov created ISPN-12652: --------------------------------------- Summary: Cluster is broken after one node is down Key: ISPN-12652 URL: https://issues.redhat.com/browse/ISPN-12652 Project: Infinispan Issue Type: Bug Affects Versions: 9.4.14.Final Reporter: Dmitry Kruglikov We have 3 nodes in cluster: app1, app2 and app3. App1 was shut down not gracefully because of some hardware issue. After that app2 and app3 started to fail with something like ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (timeout-thread--p23-t1) ISPN000136: Error executing command RemoveCommand on Cache 'fs.war', writing keys [SessionCreationMetaDataKey(PGARVVdjGKfifzrVfyd7HAllbrwaRG7wLhKha1On)]: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 422657 from app1 at org.infinispan@9.4.14.Final//org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167) at org.infinispan@9.4.14.Final//org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87) at org.infinispan@9.4.14.Final//org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) So these 2 nodes (app2 and app3) could not serve user requests anymore until app1 recovered. My question is... Is it ok? Should not Infinispan identify that one of nodes is down, remove it from cluster and notify app2 and app3 about it? I know that there is something like VERIFY_SUSPECT but it didn't happen. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12646) IllegalArgumentException when doing Rolling Upgrades on transactional caches

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12646?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12646: ------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/9007 Status: Pull Request Sent (was: Coding In Progress) > IllegalArgumentException when doing Rolling Upgrades on transactional caches > ---------------------------------------------------------------------------- > > Key: ISPN-12646 > URL: https://issues.redhat.com/browse/ISPN-12646 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.9.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > {noformat} > Caused by: java.lang.IllegalArgumentException: Cannot create a transactional context without a valid Transaction instance. > at org.infinispan.context.impl.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:63) > [...] > at org.infinispan.cache.impl.DecoratedCache.putIfAbsent(DecoratedCache.java:688) > at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.putIfAbsent(AbstractDelegatingAdvancedCache.java:328) > at org.infinispan.cache.impl.EncoderCache.putIfAbsent(EncoderCache.java:450) > at org.infinispan.persistence.remote.upgrade.MigrationTask.lambda$migrateEntriesWithMetadata$0(MigrationTask.java:128) > at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1771) > {noformat} > The migration component that obtains data from the remote cache does not use transactions to write to the destination cache, and since it runs on a separate thread, it cannot see any ongoing transaction and thus fail to write to the cache. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 8 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 2021