April 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3059) x-site's takeoffline functionality doesn't work correctly when using 1PC replication between sites

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3059: ----------------------------------- Summary: x-site's takeoffline functionality doesn't work correctly when using 1PC replication between sites Key: ISPN-3059 URL: https://issues.jboss.org/browse/ISPN-3059 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.5.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.Beta1, 5.3.0.Final When the local cluster uses 2PC but the inter-site replication is configured to use 1PC, during the local prepare, the number communication failures with remote site is reset to 0 - that should not happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3001) DeltaAwareCacheEntry.getLifespan() and getMaxIdle() return 0 and cause instant expiration

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3001?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3001: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1795 > DeltaAwareCacheEntry.getLifespan() and getMaxIdle() return 0 and cause instant expiration > ----------------------------------------------------------------------------------------- > > Key: ISPN-3001 > URL: https://issues.jboss.org/browse/ISPN-3001 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.3.0.Beta1 > > > These methods should actually return -1 if we intend this entry to live forever, not 0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3056) FineGrainedAtomicMap updates are lost on some cluster nodes when eviction or passivation is involved

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3056?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3056: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1795 > FineGrainedAtomicMap updates are lost on some cluster nodes when eviction or passivation is involved > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-3056 > URL: https://issues.jboss.org/browse/ISPN-3056 > Project: Infinispan > Issue Type: Bug > Components: Core API, Eviction, Fine-grained API > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.3.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2974) DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2974?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2974: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1795 > DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled > ------------------------------------------------------------------------------------- > > Key: ISPN-2974 > URL: https://issues.jboss.org/browse/ISPN-2974 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.1.Final, 5.2.5.Final > Reporter: Horia Chiorean > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.3.0.Beta1 > > > When using a custom {{DeltaAware}} implementation in a cluster with 2 replicated nodes with eviction enabled, data transferred from one node (the writer) to the another (the reader) causes data stored on this node and evicted at the time of the change, to be rewritten with whatever the partial latest delta was. > In more detail: > * configure 2 nodes in replicated mode, with eviction enabled > * consider NodeA the writer and NodeB the reader > * NodeA inserts some data (custom entries) into the cache > * NodeB correctly receives via state transfer the initial data > * NodeA loads & partially updates some information about an entry which was not in the cache - was evicted previously > * NodeB receives the partial delta with the changes from NodeA, but *instead of merging* with whatever is stored in the persistent store, *replaces the entire entry in the cache*, leaving it in effect with "partial/corrupt information" > If eviction is not enabled, everything works as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2996) ApplyDeltaCommand.getAffectedKeys() and ApplyDeltaCommand.getKey() do not return the expected key

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2996?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2996: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1795 > ApplyDeltaCommand.getAffectedKeys() and ApplyDeltaCommand.getKey() do not return the expected key > ------------------------------------------------------------------------------------------------- > > Key: ISPN-2996 > URL: https://issues.jboss.org/browse/ISPN-2996 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.3.0.Final > > > These methods should return the map key but null is returned instead because the super constructor is not invoked correctly. > See discussion on infinispan dev list here: http://markmail.org/message/dkoughqngztmxvuy > This class could also be simplified a bit by removing the field deltaAwareValueKey which duplicates the key field of the base class. > Also since keys are non-null (asserted by constructor) the equals() and hashCode() methods can be simplified by removing the null checks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2988) Invalid Transport.isCoordinator() usages in ClusteredActivationInterceptor and ClusteredCacheLoaderInterceptor in REPL mode

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2988?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2988: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1795 > Invalid Transport.isCoordinator() usages in ClusteredActivationInterceptor and ClusteredCacheLoaderInterceptor in REPL mode > --------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2988 > URL: https://issues.jboss.org/browse/ISPN-2988 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.3.0.Beta1 > > > Transport.isCoordinator() is used to determine if we are the primary owner but this usage is no longer valid since the introduction of asymmetric caches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2903) Manual eviction should not delete entry from cache store

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2903?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2903: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549] from POST to MODIFIED > Manual eviction should not delete entry from cache store > -------------------------------------------------------- > > Key: ISPN-2903 > URL: https://issues.jboss.org/browse/ISPN-2903 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 5.2.3.Final > Reporter: Paul Ferraro > Assignee: Galder Zamarreño > Priority: Critical > Labels: 5.2.x, jdg6 > Fix For: 5.2.5.Final, 5.3.0.Alpha1, 5.3.0.Final > > Attachments: AtomicMapServlet.java, AtomicMapTestCase.java, server.log, server.log > > > Here's the scenario: > Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7). > 1. Create cache entry containing atomic map with 2 map entries on node1. > 2. Passivate that cache entry on node2 via manual evict. > 3. Modify 1 of the atomic map entries within the cache entry on node1. > 4. Lookup atomic map on node2. It only contains 1 map entry - the map entry modified in step 3. The other map entry is lost. > It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3042) Rebase AS integration modules against EAP 6.1

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3042?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3042: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Rebase AS integration modules against EAP 6.1 > --------------------------------------------- > > Key: ISPN-3042 > URL: https://issues.jboss.org/browse/ISPN-3042 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Affects Versions: 5.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3052) Upgrade aesh to 0.33.1

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3052?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3052: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade aesh to 0.33.1 > ---------------------- > > Key: ISPN-3052 > URL: https://issues.jboss.org/browse/ISPN-3052 > Project: Infinispan > Issue Type: Component Upgrade > Components: CLI > Affects Versions: 5.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta1 > > > Currently the Infinispan Server shell breaks because it requires this more recent version -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3052) Upgrade aesh to 0.33.1

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3052?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3052: ----------------------------------- Fix Version/s: 5.3.0.Final > Upgrade aesh to 0.33.1 > ---------------------- > > Key: ISPN-3052 > URL: https://issues.jboss.org/browse/ISPN-3052 > Project: Infinispan > Issue Type: Component Upgrade > Components: CLI > Affects Versions: 5.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta1, 5.3.0.Final > > > Currently the Infinispan Server shell breaks because it requires this more recent version -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2013