August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5692) Registering a remote event listener fails if cache is indexed, uses protobuf marshalling and includeInitialState=true

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5692: ----------------------------------- Summary: Registering a remote event listener fails if cache is indexed, uses protobuf marshalling and includeInitialState=true Key: ISPN-5692 URL: https://issues.jboss.org/browse/ISPN-5692 Project: Infinispan Issue Type: Bug Components: Remote Querying Affects Versions: 7.2.4.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5692) Registering a remote event listener fails if cache is indexed, uses protobuf marshalling and includeInitialState=true

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5692?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5692: -------------------------------- Fix Version/s: 8.0.0.Final 7.2.5.Final > Registering a remote event listener fails if cache is indexed, uses protobuf marshalling and includeInitialState=true > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5692 > URL: https://issues.jboss.org/browse/ISPN-5692 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.2.4.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.CR1, 8.0.0.Final, 7.2.5.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5692) Registering a remote event listener fails if cache is indexed, uses protobuf marshalling and includeInitialState=true

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5692?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5692: -------------------------------- Status: Open (was: New) > Registering a remote event listener fails if cache is indexed, uses protobuf marshalling and includeInitialState=true > --------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5692 > URL: https://issues.jboss.org/browse/ISPN-5692 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.2.4.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.CR1, 8.0.0.Final, 7.2.5.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5691) Server should enable writeSkew for some configurations by default

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5691?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5691: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1255783 > Server should enable writeSkew for some configurations by default > ----------------------------------------------------------------- > > Key: ISPN-5691 > URL: https://issues.jboss.org/browse/ISPN-5691 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1, 8.0.0.Final, 7.2.5.Final > > > By default, optimistic locking caches do not enable write skew. This was already spotted in ISPN-3655. > In an embedded environment, the user can always enable write skew in its configuration, but this cannot be enabled in server mode. > Widlfly does enable write skew programmatically depending on the configuration: > {quote} > > hey, quick q: can you configure writeSkew on infinispan wildfly > config? > <pferraro> we always enable write skew for synchronous, optimistic, > repeatable-read caches, and disable otherwise > > pferraro: ah, you do it in the integration code? > <pferraro> yes > {quote} > We need to be doing the same in server configuration, otherwise we run the risk of having issues with conditional operations under failure situations (see ISPN-2956) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5691) Server should enable writeSkew for some configurations by default

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5691: -------------------------------------- Summary: Server should enable writeSkew for some configurations by default Key: ISPN-5691 URL: https://issues.jboss.org/browse/ISPN-5691 Project: Infinispan Issue Type: Enhancement Components: Server Reporter: Galder Zamarreño Assignee: Tristan Tarrant Fix For: 8.0.0.CR1, 8.0.0.Final, 7.2.5.Final By default, optimistic locking caches do not enable write skew. This was already spotted in ISPN-3655. In an embedded environment, the user can always enable write skew in its configuration, but this cannot be enabled in server mode. Widlfly does enable write skew programmatically depending on the configuration: {quote} > hey, quick q: can you configure writeSkew on infinispan wildfly config? <pferraro> we always enable write skew for synchronous, optimistic, repeatable-read caches, and disable otherwise > pferraro: ah, you do it in the integration code? <pferraro> yes {quote} We need to be doing the same in server configuration, otherwise we run the risk of having issues with conditional operations under failure situations (see ISPN-2956) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5690) Plain cache instances of configuration templates don't get properly persisted

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5690?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5690: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3663 > Plain cache instances of configuration templates don't get properly persisted > ----------------------------------------------------------------------------- > > Key: ISPN-5690 > URL: https://issues.jboss.org/browse/ISPN-5690 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.CR1, 8.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5689) Preserve compatibility with Hibernate 5.0.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5689?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5689: ------------------------------------ Status: Open (was: New) > Preserve compatibility with Hibernate 5.0.0.Final > ------------------------------------------------- > > Key: ISPN-5689 > URL: https://issues.jboss.org/browse/ISPN-5689 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.0.0.CR1 > > > {{org.infinispan.commands.write.AbstractDataWriteCommand}} introduced a final method {{getLockOwner()}} with the same name as a method used by a child class in Hibernate 2LC {{org.hibernate.cache.infinispan.util.BeginInvalidationCommand}} > To maintain compatibility between Infinispan 8 and Hibernate 5 (already released), that method should be renamed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5689) Preserve compatibility with Hibernate 5.0.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5689?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5689: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3662 > Preserve compatibility with Hibernate 5.0.0.Final > ------------------------------------------------- > > Key: ISPN-5689 > URL: https://issues.jboss.org/browse/ISPN-5689 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.0.0.CR1 > > > {{org.infinispan.commands.write.AbstractDataWriteCommand}} introduced a final method {{getLockOwner()}} with the same name as a method used by a child class in Hibernate 2LC {{org.hibernate.cache.infinispan.util.BeginInvalidationCommand}} > To maintain compatibility between Infinispan 8 and Hibernate 5 (already released), that method should be renamed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5553) Functional Java 8 API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5553?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5553: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Functional Java 8 API > --------------------- > > Key: ISPN-5553 > URL: https://issues.jboss.org/browse/ISPN-5553 > Project: Infinispan > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Infinispan 8 is baselining on Java 8 and that enables a more advanced , functional, APIs to be built instead of relying on the traditional Map-like APIs. Such APIs, taking lambda functions, can improve on the current APIs in the following way: > * Being able to provide a write operation, where the operation is defined as a lambda, better enables conditional (CAS) like operations that are based in functions other than equality, e.g. version equality. If this functions can be executed atomically, they provide a better solution for Hot Rod version-based replace operations that currently can cause some weird behaviour (ISPN-4972) > * When operations are defined as lambdas, it's easier to move towards a model that tracks/replicates operations leading to state, rather than replicating state itself. This makes it easier to implement more-efficiently replicated alternative data structures, such as counts, lists...etc, and paths the way towards CRDTs, particularly CmRDT (Commutative Replicated Data Types) or operation-based CRDTs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5690) Plain cache instances of configuration templates don't get properly persisted

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5690: ------------------------------------- Summary: Plain cache instances of configuration templates don't get properly persisted Key: ISPN-5690 URL: https://issues.jboss.org/browse/ISPN-5690 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 8.0.0.Beta3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 8.0.0.CR1, 8.0.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2015