January 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6476) Integration test modules shouldn't change the failsafe plugin's lifecycle

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6476?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6476: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Integration test modules shouldn't change the failsafe plugin's lifecycle > ------------------------------------------------------------------------- > > Key: ISPN-6476 > URL: https://issues.jboss.org/browse/ISPN-6476 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.7.Final > > > Many of our integration tests modules run the {{integration-test}} and {{verify}} goals of {{maven-failsafe-plugin}} together, sometimes specifying a lifecycle phase, sometimes not. This shouldn't be necessary, because failsafe runs both goals, it just binds them to different phases. > On the contrary, running both goals in the same phase can fail the build too early, skipping any executions bound to the {{post-integration-test}} phase. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9029) Add test for exception eviction dropping entries after node leave

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9029?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9029: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Add test for exception eviction dropping entries after node leave > ----------------------------------------------------------------- > > Key: ISPN-9029 > URL: https://issues.jboss.org/browse/ISPN-9029 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Major > Fix For: 9.4.7.Final > > > {{ExceptionEvictionTest}} tests what happens when a node is added and N*limit existing entries are redistributed among N+1 nodes. We also need to test what happens when a node crashes and N*limit entries are redistributed among N-1 nodes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6479) CacheRpcCommandExternalizer should cache the cache name bytes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6479: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > CacheRpcCommandExternalizer should cache the cache name bytes > ------------------------------------------------------------- > > Key: ISPN-6479 > URL: https://issues.jboss.org/browse/ISPN-6479 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9031) Add CodedInputStream.setsize functionality

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9031?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9031: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Add CodedInputStream.setsize functionality > ------------------------------------------ > > Key: ISPN-9031 > URL: https://issues.jboss.org/browse/ISPN-9031 > Project: Infinispan > Issue Type: Feature Request > Reporter: Lena Herrmann > Priority: Major > Fix For: 9.4.7.Final > > > If you want to use the Protobufmarchaller for larger objects the following exception occurs: > {code:java} > at org.infinispan.client.hotrod.marshall.MarshallerUtil.bytes2obj(MarshallerUtil.java:49) > at org.infinispan.client.hotrod.impl.protocol.CodecUtils.readUnmarshallByteArray(CodecUtils.java:38) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readUnmarshallByteArray(Codec20.java:54) > at org.infinispan.client.hotrod.impl.operations.GetOperation.executeOperation(GetOperation.java:36) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:367) > at com.channelpilot.api.tabledata.RemoteCacheConnector.get(RemoteCacheConnector.java:49) > at com.channelpilot.api.tabledata.TableDataService.get(TableDataService.java:91) > at com.channelpilot.api.tabledata.build.ControlDataBuilder.build(ControlDataBuilder.java:48) > at com.channelpilot.api.frontend.jobs.threads.BuildTableDataJob.execute(BuildTableDataJob.java:72) > at com.channelpilot.api.frontend.jobs.threads.BuildTableDataJob.execute(BuildTableDataJob.java:31) > at com.channelpilot.utils.concurrent.CPCallable.call(CPCallable.java:105) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > Caused by: protostream.com.google.protobuf.InvalidProtocolBufferException: Protocol message was too large. May be malicious. Use CodedInputStream.setSizeLimit() to increase the size limit. > at protostream.com.google.protobuf.InvalidProtocolBufferException.sizeLimitExceeded(InvalidProtocolBufferException.java:122) > at protostream.com.google.protobuf.CodedInputStream.readRawBytesSlowPath(CodedInputStream.java:1166) > at protostream.com.google.protobuf.CodedInputStream.readByteArray(CodedInputStream.java:535) > at org.infinispan.protostream.impl.RawProtoStreamReaderImpl.readByteArray(RawProtoStreamReaderImpl.java:105) > at org.infinispan.protostream.WrappedMessage.readMessage(WrappedMessage.java:232) > at org.infinispan.protostream.ProtobufUtil.fromWrappedByteArray(ProtobufUtil.java:122) > at org.infinispan.query.remote.client.BaseProtoStreamMarshaller.objectFromByteBuffer(BaseProtoStreamMarshaller.java:32) > at org.infinispan.commons.marshall.AbstractMarshaller.objectFromByteBuffer(AbstractMarshaller.java:82) > at org.infinispan.client.hotrod.marshall.MarshallerUtil.bytes2obj(MarshallerUtil.java:33) > {code} > According to the official protobuf-documentation one should increase the size-limit, if this exception is thrown. Within infinispan there is no possibility to change this size in some way. > Adding the to for example a configurationbuilder or similar, would be a good improvement. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6585) Persistence support in functional API

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6585?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6585: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Persistence support in functional API > ------------------------------------- > > Key: ISPN-6585 > URL: https://issues.jboss.org/browse/ISPN-6585 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9054) Upgrade to Aesh 1.0

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9054?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9054: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Upgrade to Aesh 1.0 > ------------------- > > Key: ISPN-9054 > URL: https://issues.jboss.org/browse/ISPN-9054 > Project: Infinispan > Issue Type: Component Upgrade > Components: CLI > Reporter: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > Aesh 1.0 has been released, and is currently used by Wildfly 12.x. 1.0 has several differences to Aesh 0.66.x, most notably the introduction of the aesh-readline project and the removal of AeshConsoleCallback. The upgrade is non-trivial, however due to some of the new features provided by Aesh 1.x, it could greatly reduce the amount of code required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9072) Document Protobuf annotated collection null set callbacks

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9072?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9072: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Document Protobuf annotated collection null set callbacks > --------------------------------------------------------- > > Key: ISPN-9072 > URL: https://issues.jboss.org/browse/ISPN-9072 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Affects Versions: 9.2.1.Final > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.7.Final > > > When using collection fields in Protobuf annotated classes, empty collections are marshalled into the same value as {{null}}, because Protobuf only has repeated fields and no fields is represented as {{null}}. > This means that if you have an entity with an empty collection, when it's deserialized the collection will be null. This can be confusing for users and should be documented. > [~anistor] had some ideas on how to improve this: > {code} > <anistor> I'm thinking of a way to make this easier for users that > would prefer an empty collection being set instead of a > null. would be possible by adding a new attribute for this in > @ProtoField anotation > > that'd be more predictable > <anistor> would still not give you at deserializtion what was written > during serialization. we do not have a null marker > <anistor> it would just give you an empty collection if you prefer > <anistor> instead of null > > that option should be enabled by default > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6635) Multi tenancy

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6635?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6635: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Multi tenancy > ------------- > > Key: ISPN-6635 > URL: https://issues.jboss.org/browse/ISPN-6635 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Major > Fix For: 9.4.7.Final > > > Hosting Infinispan as a Service requires support of multi tenancy. > The design for this feature might be found here: https://github.com/infinispan/infinispan/wiki/Multi-tenancy-for-Hotrod-Se... > And implementation plan in the subtasks. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9079) Cache operations during Conflict Resolution phase should force CR on that key

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9079?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9079: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Cache operations during Conflict Resolution phase should force CR on that key > ----------------------------------------------------------------------------- > > Key: ISPN-9079 > URL: https://issues.jboss.org/browse/ISPN-9079 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > During a partition merge conflict resolution can take a long time when there are many entries, therefore if a user initiates an operation on a key during this phase, it should force CR to occur on the key before executing the operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9112) getCache() should not wait for the initial state transfer by default

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9112?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9112: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > getCache() should not wait for the initial state transfer by default > -------------------------------------------------------------------- > > Key: ISPN-9112 > URL: https://issues.jboss.org/browse/ISPN-9112 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.7.Final > > > {{DefaultCacheManager.getCache(name)}} normally blocks until the local node becomes a full member of the consistent hash and the rebalance has finished. This can cause problems when rebalancing is disabled, either explicitly by the administrator, or implicitly because the cache is in degraded mode. > Blocking can be disabled with {{builder.clustering().stateTransfer().awaitInitialTransfer(false)}} ({{await-initial-transfer="false"}} in XML}}, but we should make the non-blocking behaviour the default. We should also deprecate the method and attribute to enable the blocking behaviour, and instead add a method to {{AdvancedCache}} to wait for the initial state transfer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2019