March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6326) Tasks should log to the event log optionally

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6326?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6326: ------------------------------------- Assignee: Tristan Tarrant > Tasks should log to the event log optionally > -------------------------------------------- > > Key: ISPN-6326 > URL: https://issues.jboss.org/browse/ISPN-6326 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > We only want console invocations of a task to generate an event log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6254) State transfer hangs after CacheNotFoundResponse

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6254?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-6254. -------------------------------- Resolution: Done The warning was fixed with ISPN-6327. > State transfer hangs after CacheNotFoundResponse > ------------------------------------------------ > > Key: ISPN-6254 > URL: https://issues.jboss.org/browse/ISPN-6254 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.Beta2, 8.1.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 8.2.0.Final, 8.2.0.CR1 > > > When {{StateConsumerImpl.addTransfer()}} sends a {{StateRequestCommand(START_STATE_TRANSFER)}}, it doesn't block the thread until it receives all the state (ISPN-5019). Instead, it calls {{SemaphoreCompletionService.continueTaskInBackground()}}, and then it calls {{SemaphoreCompletionService.backgroundTaskFinished()}} when it receives the response. > However, if the request wasn't successful, e.g. because the node providing the state is shutting down and replies with a {{CacheNotFoundResponse}}, {{SemaphoreCompletionService.backgroundTaskFinished()}} isn't called, and state transfer cannot make any progress. > This shows up in the test suite as random failures in {{NumOwnersNodeCrashInSequenceTest}} and {{NumOwnersNodeStopInSequenceTest}}: > {noformat} > 17:49:16,960 ERROR (testng-NumOwnersNodeCrashInSequenceTest:) [UnitTestTestNGListener] Test testNodeCrashedBeforeStFinished0(org.infinispan.partitionhandling.NumOwnersNodeCrashInSequenceTest) failed. > org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.Exception on object of type StateTransferManagerImpl > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172) ~[infinispan-commons-8.2.0-SNAPSHOT.jar:8.2.0-SNAPSHOT] > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:887) ~[classes/:?] > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:656) ~[classes/:?] > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:645) ~[classes/:?] > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:548) ~[classes/:?] > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:222) ~[classes/:?] > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:849) ~[classes/:?] > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:624) ~[classes/:?] > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:577) ~[classes/:?] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:445) ~[classes/:?] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:431) ~[classes/:?] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:413) ~[classes/:?] > at org.infinispan.test.MultipleCacheManagersTest.getCaches(MultipleCacheManagersTest.java:211) ~[test-classes/:?] > at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:220) ~[test-classes/:?] > at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:229) ~[test-classes/:?] > at org.infinispan.partitionhandling.NumOwnersNodeCrashInSequenceTest.testNodeCrashedBeforeStFinished(NumOwnersNodeCrashInSequenceTest.java:105) ~[test-classes/:?] > at org.infinispan.partitionhandling.NumOwnersNodeCrashInSequenceTest.testNodeCrashedBeforeStFinished0(NumOwnersNodeCrashInSequenceTest.java:67) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6327) InboundTransferTask erroneously log CacheException for successful responses

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6327?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6327: ------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Gustavo Fernandes Resolution: Done > InboundTransferTask erroneously log CacheException for successful responses > --------------------------------------------------------------------------- > > Key: ISPN-6327 > URL: https://issues.jboss.org/browse/ISPN-6327 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6329) Add Infinispan Core to Remote Uber Jar

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6329?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6329: -------------------------------------- Status: Open (was: New) > Add Infinispan Core to Remote Uber Jar > -------------------------------------- > > Key: ISPN-6329 > URL: https://issues.jboss.org/browse/ISPN-6329 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 8.2.0.CR1 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 8.2.0.Final > > > We need to support Remote Cache Scenario in this type of deployment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6329) Add Infinispan Core to Remote Uber Jar

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6329?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6329: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4082 > Add Infinispan Core to Remote Uber Jar > -------------------------------------- > > Key: ISPN-6329 > URL: https://issues.jboss.org/browse/ISPN-6329 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 8.2.0.CR1 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 8.2.0.Final > > > We need to support Remote Cache Scenario in this type of deployment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6329) Add Infinispan Core to Remote Uber Jar

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6329: ----------------------------------------- Summary: Add Infinispan Core to Remote Uber Jar Key: ISPN-6329 URL: https://issues.jboss.org/browse/ISPN-6329 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 8.2.0.CR1 Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Fix For: 8.2.0.Final We need to support Remote Cache Scenario in this type of deployment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6038) ClientAsymmetricClusterTest.testAsymmetricCluster random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6038?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6038: ------------------------------------------- Ignored by: https://github.com/infinispan/infinispan/pull/4081 > ClientAsymmetricClusterTest.testAsymmetricCluster random failures > ----------------------------------------------------------------- > > Key: ISPN-6038 > URL: https://issues.jboss.org/browse/ISPN-6038 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Test Suite - Server > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Priority: Minor > Labels: testsuite_stability > Fix For: 8.2.0.Final > > > {{ClientAsymmetricClusterTest.testAsymmetricCluster}} is failing since the ISPN-5981 fix, which enabled {{pingOnStartup}} by default, and now returns {{null}} if the first server to be pinged doesn't have the cache defined. > {noformat} > 10:23:07,862 WARN (testng-ClientAsymmetricClusterTest:) [Codec21] ISPN004005: Error received from the server: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'asymmetricCache' not found amongst the configured caches > 10:23:07,862 ERROR (testng-ClientAsymmetricClusterTest:) [UnitTestTestNGListener] Test testAsymmetricCluster(org.infinispan.client.hotrod.ClientAsymmetricClusterTest) failed. > java.lang.NullPointerException > at org.infinispan.client.hotrod.ClientAsymmetricClusterTest.testAsymmetricCluster(ClientAsymmetricClusterTest.java:38) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6328) Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6328?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6328: -------------------------------- Status: Open (was: New) > Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero) > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-6328 > URL: https://issues.jboss.org/browse/ISPN-6328 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.2.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Final > > > Running queries on a remote cache that was previously populated by an app that did not use protobuf marshalling should be allowed, and all those entities that were not encoded using protobuf should be ignored by the query engine and a warning should be logged instructing the user about the potential issue and how to fix the configuration. > The current behaviour in this case is not user friendly, especially in case of non-indexed query. An error is thrown during query evaluation: "com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)." which indicates the unmarshalling of the queried entities is not possible. The actual cause of the bad encoding should be explained to the user and no exception should be thrown as if the type of entities does not match the requested type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6328) Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6328: ----------------------------------- Summary: Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero) Key: ISPN-6328 URL: https://issues.jboss.org/browse/ISPN-6328 Project: Infinispan Issue Type: Bug Components: Remote Querying Affects Versions: 8.2.0.CR1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.2.0.Final Running queries on a remote cache that was previously populated by an app that did not use protobuf marshalling should be allowed, and all those entities that were not encoded using protobuf should be ignored by the query engine and a warning should be logged instructing the user about the potential issue and how to fix the configuration. The current behaviour in this case is not user friendly, especially in case of non-indexed query. An error is thrown during query evaluation: "com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)." which indicates the unmarshalling of the queried entities is not possible. The actual cause of the bad encoding should be explained to the user and no exception should be thrown as if the type of entities does not match the requested type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6327) InboundTransferTask erroneously log CacheException for successful responses

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6327?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6327: ------------------------------------ Status: Open (was: New) > InboundTransferTask erroneously log CacheException for successful responses > --------------------------------------------------------------------------- > > Key: ISPN-6327 > URL: https://issues.jboss.org/browse/ISPN-6327 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Fix For: 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016