June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9284) Near-Real-Time indexes lost when server is stopped

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created ISPN-9284: -------------------------------------- Summary: Near-Real-Time indexes lost when server is stopped Key: ISPN-9284 URL: https://issues.jboss.org/browse/ISPN-9284 Project: Infinispan Issue Type: Bug Components: Indexing, Server Reporter: Wolf-Dieter Fink Assignee: Gustavo Fernandes The server does not respect the stop order of the caches dictated by cache manager and tries to stop all caches in random order. When a cache is indexed and uses the "near-real-time" index manager, it relies on the indexing caches being available during shutdown of the data cache so that it can properly flush the index to persistence storage, and this fails due to one or more index caches being unavailable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9262) Make javax.transaction dependency really provided

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9262?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-9262: ----------------------------------- [~galder.zamarreno] I was wrong and the {{javax.transaction}} dependency must be there. I added {{TransactionManager getTransactionManager()}} method to the {{RemoteCache}} interface to be symmetric with embedded mode. I'll close this JIRA. > Make javax.transaction dependency really provided > ------------------------------------------------- > > Key: ISPN-9262 > URL: https://issues.jboss.org/browse/ISPN-9262 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Fix For: 9.3.0.Final > > > Follow up to ISPN-9258, javax.transaction dependency should only be needed when user is using the corresponding APIs. > Marking the dependency as provided is not enough, the code should be modularized so that the client code that deals with transactions depending on javax.transaction is only loaded when such APIs are used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9262) Make javax.transaction dependency really provided

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9262?page=com.atlassian.jira.plugin.... ] Pedro Ruivo closed ISPN-9262. ----------------------------- Resolution: Rejected > Make javax.transaction dependency really provided > ------------------------------------------------- > > Key: ISPN-9262 > URL: https://issues.jboss.org/browse/ISPN-9262 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Fix For: 9.3.0.Final > > > Follow up to ISPN-9258, javax.transaction dependency should only be needed when user is using the corresponding APIs. > Marking the dependency as provided is not enough, the code should be modularized so that the client code that deals with transactions depending on javax.transaction is only loaded when such APIs are used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9282) Near-Real-Time indexes lost when server is stopped

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9282?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-9282: --------------------------------------- Assignee: Gustavo Fernandes > Near-Real-Time indexes lost when server is stopped > -------------------------------------------------- > > Key: ISPN-9282 > URL: https://issues.jboss.org/browse/ISPN-9282 > Project: Infinispan > Issue Type: Bug > Components: Indexing, Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The server does not respect the stop order of the caches dictated by cache manager and tries to stop all caches in random order. > When a cache is indexed and uses the "near-real-time" index manager, it relies on the indexing caches being available during shutdown of the data cache so that it can properly flush the index to persistence storage, and this fails due to one or more index caches being unavailable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9282) Near-Real-Time indexes lost when server is stopped

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9282?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9282: ------------------------------------ Status: Open (was: New) > Near-Real-Time indexes lost when server is stopped > -------------------------------------------------- > > Key: ISPN-9282 > URL: https://issues.jboss.org/browse/ISPN-9282 > Project: Infinispan > Issue Type: Bug > Components: Indexing, Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The server does not respect the stop order of the caches dictated by cache manager and tries to stop all caches in random order. > When a cache is indexed and uses the "near-real-time" index manager, it relies on the indexing caches being available during shutdown of the data cache so that it can properly flush the index to persistence storage, and this fails due to one or more index caches being unavailable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9282) Near-Real-Time indexes lost when server is stopped

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9282?page=com.atlassian.jira.plugin.... ] Work on ISPN-9282 started by Gustavo Fernandes. ----------------------------------------------- > Near-Real-Time indexes lost when server is stopped > -------------------------------------------------- > > Key: ISPN-9282 > URL: https://issues.jboss.org/browse/ISPN-9282 > Project: Infinispan > Issue Type: Bug > Components: Indexing, Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The server does not respect the stop order of the caches dictated by cache manager and tries to stop all caches in random order. > When a cache is indexed and uses the "near-real-time" index manager, it relies on the indexing caches being available during shutdown of the data cache so that it can properly flush the index to persistence storage, and this fails due to one or more index caches being unavailable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9277) Put & Get call is not in sync

by paragBorah Borah (JIRA)

[ https://issues.jboss.org/browse/ISPN-9277?page=com.atlassian.jira.plugin.... ] paragBorah Borah commented on ISPN-9277: ---------------------------------------- [~dan.berindei] Thanks a lot for Quick reply. This information is valuable to us. I have another Question, With the same configuration in infinispan 9.1.1, if we use cache.putAsync(key, value) with Async cache, Does local cache will behave as Sync & replication to behave as Async ? or both will behave as Async. If we have to make local cache only Sync & replicated as Async what steps need to do? > Put & Get call is not in sync > ----------------------------- > > Key: ISPN-9277 > URL: https://issues.jboss.org/browse/ISPN-9277 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.1.Final > Reporter: paragBorah Borah > Priority: Blocker > Attachments: newConfig911.txt, oldConfig722.txt > > > Hello, > We have upgraded infinispan cache from 7.2.2 to 9.1.1. > We have configuration (old config file) where we have <local-cache> & <replicated-cache> with same name as “defaultcache”. Where in latest version 9.1.1 we can’t have same name. > Now my concern is about configuration. In previous configuration when we perform put operation & in some time get operation giving us the latest data from cache. > But in latest version after put operation & in some time get operation is not giving the latest updated data from cache. > Could you please help me with the configuration details which can help me to fix this issue. > Regards > Parag > > [~NadirX] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9264) StringBasedStoreInvalidationCacheSyncIT Failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9264?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9264: ------------------------------- Status: Open (was: New) > StringBasedStoreInvalidationCacheSyncIT Failures > ------------------------------------------------ > > Key: ISPN-9264 > URL: https://issues.jboss.org/browse/ISPN-9264 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.3.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > {code:java} > testRemoveNonExistentEntry > java.lang.AssertionError: Read timeout at org.infinispan.server.test.cs.jdbc.multinode.StringBasedStoreInvalidationCacheSyncIT.testRemoveNonExistentEntry(StringBasedStoreInvalidationCacheSyncIT.java:82) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9264) StringBasedStoreInvalidationCacheSyncIT Failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9264?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9264: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6052 > StringBasedStoreInvalidationCacheSyncIT Failures > ------------------------------------------------ > > Key: ISPN-9264 > URL: https://issues.jboss.org/browse/ISPN-9264 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.3.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > {code:java} > testRemoveNonExistentEntry > java.lang.AssertionError: Read timeout at org.infinispan.server.test.cs.jdbc.multinode.StringBasedStoreInvalidationCacheSyncIT.testRemoveNonExistentEntry(StringBasedStoreInvalidationCacheSyncIT.java:82) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9277) Put & Get call is not in sync

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9277?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-9277. -------------------------------- Resolution: Explained > Put & Get call is not in sync > ----------------------------- > > Key: ISPN-9277 > URL: https://issues.jboss.org/browse/ISPN-9277 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.1.Final > Reporter: paragBorah Borah > Priority: Blocker > Attachments: newConfig911.txt, oldConfig722.txt > > > Hello, > We have upgraded infinispan cache from 7.2.2 to 9.1.1. > We have configuration (old config file) where we have <local-cache> & <replicated-cache> with same name as “defaultcache”. Where in latest version 9.1.1 we can’t have same name. > Now my concern is about configuration. In previous configuration when we perform put operation & in some time get operation giving us the latest data from cache. > But in latest version after put operation & in some time get operation is not giving the latest updated data from cache. > Could you please help me with the configuration details which can help me to fix this issue. > Regards > Parag > > [~NadirX] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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