March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9013) Partition Handling enabled toggle should set merge-policy=NONE

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9013?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9013: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.2.Final 9.3.0.Alpha1 Resolution: Done > Partition Handling enabled toggle should set merge-policy=NONE > -------------------------------------------------------------- > > Key: ISPN-9013 > URL: https://issues.jboss.org/browse/ISPN-9013 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.2.Final, 9.3.0.Alpha1 > > > If a user utilises the deprecated PartitionHandlingConfiguration "enabled" field, then the configured merge policy should be NONE as conflict resolution was not available in previous versions of Infinispan. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9016: --------------------------------------- [~anistor] mentioned an annotation processor approach to this which would generate a Java class instead of a serialised binary. > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9016: ------------------------------- Status: Open (was: Pull Request Sent) I overlooked the `serialVersionUUID` that's already there, so there must be another reason why metadata loading still fails when running tests from the IDE. > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-9016 at 3/29/18 1:26 AM: ------------------------------------------------------------- I overlooked the {{serialVersionUUID}} that's already there, so there must be another reason why metadata loading still fails when running tests from the IDE. was (Author: dan.berindei): I overlooked the `serialVersionUUID` that's already there, so there must be another reason why metadata loading still fails when running tests from the IDE. > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Dan Berindei closed ISPN-9016. ------------------------------ Resolution: Out of Date > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9016: ------------------------------- Status: Open (was: New) > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9016: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5881 > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

Dan Berindei created ISPN-9016: ---------------------------------- Summary: Component metadata serialization format changes depending on compiler Key: ISPN-9016 URL: https://issues.jboss.org/browse/ISPN-9016 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.2.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Fix For: 9.3.0.Alpha1 The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9005) CounterManagerOperationTest and RemoteCounterManagerTest random failures

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9005?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9005: ------------------------------ Fix Version/s: (was: 9.3.0.Alpha1) > CounterManagerOperationTest and RemoteCounterManagerTest random failures > ------------------------------------------------------------------------ > > Key: ISPN-9005 > URL: https://issues.jboss.org/browse/ISPN-9005 > Project: Infinispan > Issue Type: Bug > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.2.2.Final > > > There is a small issue in the test where the {{createCacheManagers()}} ca run before {{cleanup()}}. > It reads the counters created from the previous runs and loads them in memory. The test fails because it is expecting to not finding the counter there. > We need to make sure we cleanup before the cache manager starts. Probably is also better to cleanup after the tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8494) Clear is leaking transaction with Batching

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8494?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8494: ------------------------------ Fix Version/s: 9.2.2.Final (was: 9.3.0.Alpha1) > Clear is leaking transaction with Batching > ------------------------------------------ > > Key: ISPN-8494 > URL: https://issues.jboss.org/browse/ISPN-8494 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.2.2.Final > > > When batching is enabled, the clear() tries to suspend the running transaction but it ends leaking the internal transaction used in the batch. > {code:java} > public void testClearInBatch() { > Cache<String, String> cache = createCache("testClearInBatch"); > cache.put("k2", "value2"); > cache.startBatch(); > cache.clear(); > cache.put("k1", "value1"); > cache.endBatch(true); > // the tx is leaked and it tries to execute the get() against a committed transaction. > AssertJUnit.assertEquals(null, cache.get("k2")); > AssertJUnit.assertEquals("value1", cache.get("k1")); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018