December 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8579) CacheNotFoundException error too noisy

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8579?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8579: ------------------------------- Fix Version/s: 9.2.0.CR1 (was: 9.2.0.Beta2) > CacheNotFoundException error too noisy > -------------------------------------- > > Key: ISPN-8579 > URL: https://issues.jboss.org/browse/ISPN-8579 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 9.2.0.Beta1, 9.1.3.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.0.CR1, 9.2.0.Final > > > For JCache Remote, creating a cache requires checking first of the cache exists server side, and if not create one using admin operations. > From the server perspective, if the cache is not defined, a noisy exception is logged: > {code} > 11:52:22,361 ERROR [org.infinispan.server.hotrod.CacheDecodeContext] (HotRod-ServerWorker-4-5) ISPN005003: Exception reported: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'org.jsr107.tck.event.CacheListenerTest' not found amongst the configured caches > at org.infinispan.server.hotrod.CacheDecodeContext.obtainCache(CacheDecodeContext.java:289) > {code} > This is too noisy. The server should log something, on debug maybe but we should not treat this as an error. The client already knows that the cache returned is null, so it needs to create the cache in the server somehow, that should be enough. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8575) Add counters to willdfly-modules

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8575?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8575: ------------------------------- Fix Version/s: 9.2.0.CR1 (was: 9.2.0.Beta2) > Add counters to willdfly-modules > -------------------------------- > > Key: ISPN-8575 > URL: https://issues.jboss.org/browse/ISPN-8575 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 9.2.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8571) Compatibility with JCache 1.1

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8571?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8571: ------------------------------- Fix Version/s: 9.2.0.CR1 (was: 9.2.0.Beta2) > Compatibility with JCache 1.1 > ----------------------------- > > Key: ISPN-8571 > URL: https://issues.jboss.org/browse/ISPN-8571 > Project: Infinispan > Issue Type: Enhancement > Components: JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.0.CR1, 9.2.0.Final > > > Be compatible with upcoming JCache 1.1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8630) Integration tests should start server in the pre-integration-test phase

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8630?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8630: ------------------------------- Fix Version/s: 9.2.0.CR1 (was: 9.2.0.Beta2) > Integration tests should start server in the pre-integration-test phase > ----------------------------------------------------------------------- > > Key: ISPN-8630 > URL: https://issues.jboss.org/browse/ISPN-8630 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.CR1 > > > Some profiles in {{infinispan-server-testsuite}} require an external server, started with {{maven-antrun-plugin}} in the {{generate-test-resources}} phase. As the server might require resources modified in the {{process-test-resources}} phase, it's best to start the server in the {{pre-integration-test}} phase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8627) Add CacheContainerAdmin.getOrCreateCache() method

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8627?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8627: ------------------------------- Fix Version/s: 9.2.0.CR1 (was: 9.2.0.Beta2) > Add CacheContainerAdmin.getOrCreateCache() method > ------------------------------------------------- > > Key: ISPN-8627 > URL: https://issues.jboss.org/browse/ISPN-8627 > Project: Infinispan > Issue Type: Bug > Components: Core, Hot Rod > Affects Versions: 9.2.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.CR1 > > > CacheContainerAdmin has a createCache method which fails if the cache already exists. To make the life of developers easier, it should also have a getOrCreateCache() which returns an existing cache if possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8396) Add interceptor preventing going out of memory

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8396?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8396: ------------------------------------- EvictionStrategy is not currently used by memory configuration. But we could revamp it for that purpose. > Add interceptor preventing going out of memory > ---------------------------------------------- > > Key: ISPN-8396 > URL: https://issues.jboss.org/browse/ISPN-8396 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud, Core > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > We need an interceptor which will calculate the amount of required memory for PUT and report an error if that put will cause going out of memory. > Note that this is strictly connected to eviction mechanism (we might want to evict some entries on write) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8616) DistAsyncFuncTest.testMergeFromNonOwner random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8616?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8616: ------------------------------- Status: Open (was: New) > DistAsyncFuncTest.testMergeFromNonOwner random failures > ------------------------------------------------------- > > Key: ISPN-8616 > URL: https://issues.jboss.org/browse/ISPN-8616 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Ryan Emerson > Labels: testsuite_stability > > {noformat} > java.lang.AssertionError: Fail on owner cache DistAsyncFuncTest[DIST_ASYNC, tx=false]-NodeA-42474: dc.get(k1) returned null > at org.infinispan.distribution.BaseDistFunctionalTest.assertOwnershipAndNonOwnership(BaseDistFunctionalTest.java:191) > at org.infinispan.distribution.BaseDistFunctionalTest.assertOnAllCachesAndOwnership(BaseDistFunctionalTest.java:162) > at org.infinispan.distribution.BaseDistFunctionalTest.initAndTest(BaseDistFunctionalTest.java:142) > at org.infinispan.distribution.DistSyncFuncTest.testMergeFromNonOwner(DistSyncFuncTest.java:387) > {noformat} > The test method is new and the interceptors have changed, but it's probably the same problem with {{asyncWait}} signaled in ISPN-3741. I commented out the entire implementation of {{asyncWait}} in {{DistAsyncFuncTest}} and it still passed when run by itself, so we need a way to delay the commands and check that the test is not sensitive to such delays. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8637) ReadAfterLostDataTest.testPutMap

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-8637: --------------------------------- Summary: ReadAfterLostDataTest.testPutMap Key: ISPN-8637 URL: https://issues.jboss.org/browse/ISPN-8637 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Reporter: Pedro Ruivo Assignee: Pedro Ruivo assert fails: {code:java} Caused by: java.lang.AssertionError: SegmentBasedCollector{id=56430, topologyId=13, primaryResult=null, primaryResultReceived=false, backups={ReadAfterLostDataTest[DIST_SYNC]-NodeD-52928=[118], ReadAfterLostDataTest[DIST_SYNC]-NodeB-35269=[212, 86], ReadAfterLostDataTest[DIST_SYNC]-NodeC-19848=[252]}} {code} I need to investigate further, but I guess it is OK to replace the collector if the new has a topology id higher. the collector ignores acks from old topologies anyway. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8637) ReadAfterLostDataTest.testPutMap failure

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8637?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8637: ------------------------------ Summary: ReadAfterLostDataTest.testPutMap failure (was: ReadAfterLostDataTest.testPutMap) > ReadAfterLostDataTest.testPutMap failure > ---------------------------------------- > > Key: ISPN-8637 > URL: https://issues.jboss.org/browse/ISPN-8637 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > assert fails: > {code:java} > Caused by: java.lang.AssertionError: SegmentBasedCollector{id=56430, topologyId=13, primaryResult=null, primaryResultReceived=false, backups={ReadAfterLostDataTest[DIST_SYNC]-NodeD-52928=[118], ReadAfterLostDataTest[DIST_SYNC]-NodeB-35269=[212, 86], ReadAfterLostDataTest[DIST_SYNC]-NodeC-19848=[252]}} > {code} > I need to investigate further, but I guess it is OK to replace the collector if the new has a topology id higher. the collector ignores acks from old topologies anyway. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8120) Listeners to configuration attribute clustering.remoteTimeout are never called

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8120?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8120: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Listeners to configuration attribute clustering.remoteTimeout are never called > ------------------------------------------------------------------------------ > > Key: ISPN-8120 > URL: https://issues.jboss.org/browse/ISPN-8120 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Final > > > In order to preserve backwards compatibility, the clustering configuration forwards {{remoteTimeout(...)}} to {{syncConfiguration.replTimeout(...)}}. But that means the {{REMOTE_TIMEOUT}} attribute is never updated, and change listeners added for that attribute are never called. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2017