June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8431) ScatteredSplitAndMergeTest random failures

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8431?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-8431: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ScatteredSplitAndMergeTest random failures > ------------------------------------------ > > Key: ISPN-8431 > URL: https://issues.jboss.org/browse/ISPN-8431 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Alpha1 > Environment: Jenkins > Reporter: Tristan Tarrant > Assignee: Radim Vansa > Labels: testsuite_stability > Fix For: 9.4.0.Final > > Attachments: ScatteredSplitAndMergeTest_20180129.log.gz, ScatteredSplitAndMergeTest_ISPN-7919_RpcManager_ResponseCollector_20171212.log.gz > > > http://ci.infinispan.org/job/Infinispan/job/master/214/testReport/junit/o... > java.lang.AssertionError: expected [null] but found [v0] > at org.infinispan.partitionhandling.ScatteredSplitAndMergeTest.testSplitAndMerge(ScatteredSplitAndMergeTest.java:80) > at org.infinispan.partitionhandling.ScatteredSplitAndMergeTest.testSplitAndMerge5(ScatteredSplitAndMergeTest.java:51) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ... Removed 20 stack frames > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9324) Upgrade JTA API to 1.2

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9324?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-9324: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6095 > Upgrade JTA API to 1.2 > ---------------------- > > Key: ISPN-9324 > URL: https://issues.jboss.org/browse/ISPN-9324 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build, Transactions > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.4.0.Alpha1 > > > We should upgrade > - org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.1.Final > to > - org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.1.Final > Apparently the only significant change is that it includes more annotations; would be useful to upgrade to avoid having to play with dependency exclusions as many other platforms are using JTA 1.2 nowadays. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9324) Upgrade JTA API to 1.2

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-9324: ------------------------------------- Summary: Upgrade JTA API to 1.2 Key: ISPN-9324 URL: https://issues.jboss.org/browse/ISPN-9324 Project: Infinispan Issue Type: Component Upgrade Components: Build, Transactions Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 9.4.0.Alpha1 We should upgrade - org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.1.Final to - org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.1.Final Apparently the only significant change is that it includes more annotations; would be useful to upgrade to avoid having to play with dependency exclusions as many other platforms are using JTA 1.2 nowadays. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9324) Upgrade JTA API to 1.2

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9324?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-9324: ---------------------------------- Status: Open (was: New) > Upgrade JTA API to 1.2 > ---------------------- > > Key: ISPN-9324 > URL: https://issues.jboss.org/browse/ISPN-9324 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build, Transactions > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.4.0.Alpha1 > > > We should upgrade > - org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.1.Final > to > - org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.1.Final > Apparently the only significant change is that it includes more annotations; would be useful to upgrade to avoid having to play with dependency exclusions as many other platforms are using JTA 1.2 nowadays. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-3906. --------------------------------- Resolution: Won't Fix Given the many changes in the area of transcoding, this can no longer be done, nor is really necessary. The wrapping of the byte[] is also needed after the introduction of off-heap. So we can consider this issue obsolete. > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3906: -------------------------------- Fix Version/s: (was: 9.4.0.Final) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8482) Projection of enum field returns number instead of constant

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8482?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8482: -------------------------------- Fix Version/s: 9.4.0.Alpha1 > Projection of enum field returns number instead of constant > ----------------------------------------------------------- > > Key: ISPN-8482 > URL: https://issues.jboss.org/browse/ISPN-8482 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Fix For: 9.4.0.Alpha1 > > > Consider the query below where Gender is mapped in protobuf as an {{enum}}: > {code:sql} > select p.gender, count(p.name) from Person p group by p.gender > {code} > The returned projection is numeric rather than MALE/FEMALE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6177) Add ability to pre-register protobuf schema definitions via config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6177?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-6177. --------------------------------- Fix Version/s: 9.3.0.Final Resolution: Won't Do > Add ability to pre-register protobuf schema definitions via config > ------------------------------------------------------------------ > > Key: ISPN-6177 > URL: https://issues.jboss.org/browse/ISPN-6177 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.3.0.Final > > > The global config should name some *.proto files (from disk or CP resources) to be registered with the ProtobufMetadataManager on startup. > This could probably use org.jboss.as.server.deployment.DeploymentUnitProcessor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6177) Add ability to pre-register protobuf schema definitions via config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6177?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6177: ------------------------------------- This issue was solved by the newly added ProtostreamSerializationContextInitializer. It's a programmatic API rather than a config, but it serves the same purpose. See https://github.com/infinispan/infinispan/blob/master/remote-query/remote-... > Add ability to pre-register protobuf schema definitions via config > ------------------------------------------------------------------ > > Key: ISPN-6177 > URL: https://issues.jboss.org/browse/ISPN-6177 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.3.0.Final > > > The global config should name some *.proto files (from disk or CP resources) to be registered with the ProtobufMetadataManager on startup. > This could probably use org.jboss.as.server.deployment.DeploymentUnitProcessor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9031?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9031: -------------------------------- Fix Version/s: 9.4.0.Alpha1 > Add CodedInputStream.setsize functionality > ------------------------------------------ > > Key: ISPN-9031 > URL: https://issues.jboss.org/browse/ISPN-9031 > Project: Infinispan > Issue Type: Feature Request > Reporter: Lena Herrmann > Fix For: 9.4.0.Alpha1 > > > 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.5.0#75005)

7 years, 9 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 June 2018