August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5519) Cannot choose to run index-less query on an indexed cache in compat mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5519?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5519: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1253606|https://bugzilla.redhat.com/show_bug.cgi?id=1253606] from POST to MODIFIED > Cannot choose to run index-less query on an indexed cache in compat mode > ------------------------------------------------------------------------ > > Key: ISPN-5519 > URL: https://issues.jboss.org/browse/ISPN-5519 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.Alpha2, 7.2.3.Final > > > This is similar to ISPN-5165 but refers to compat mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5694) Server susbsystems should use homogenous logging projectCodes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5694?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5694: ---------------------------------- Status: Open (was: New) > Server susbsystems should use homogenous logging projectCodes > ------------------------------------------------------------- > > Key: ISPN-5694 > URL: https://issues.jboss.org/browse/ISPN-5694 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Beta3 > Reporter: Tristan Tarrant > Fix For: 8.0.0.Final > > > Align the three server subsystems to use homogeneous projectCodes: > JGroups: DGJGRP > Infinispan: DGISPN > Endpoint: DGENDPT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5694) Server susbsystems should use homogenous logging projectCodes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5694?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-5694: ------------------------------------- Assignee: Tristan Tarrant > Server susbsystems should use homogenous logging projectCodes > ------------------------------------------------------------- > > Key: ISPN-5694 > URL: https://issues.jboss.org/browse/ISPN-5694 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.Final > > > Align the three server subsystems to use homogeneous projectCodes: > JGroups: DGJGRP > Infinispan: DGISPN > Endpoint: DGENDPT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5694) Server susbsystems should use homogenous logging projectCodes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5694?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5694: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3667 > Server susbsystems should use homogenous logging projectCodes > ------------------------------------------------------------- > > Key: ISPN-5694 > URL: https://issues.jboss.org/browse/ISPN-5694 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.Final > > > Align the three server subsystems to use homogeneous projectCodes: > JGroups: DGJGRP > Infinispan: DGISPN > Endpoint: DGENDPT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5694) Server susbsystems should use homogenous logging projectCodes

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5694: ------------------------------------- Summary: Server susbsystems should use homogenous logging projectCodes Key: ISPN-5694 URL: https://issues.jboss.org/browse/ISPN-5694 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 8.0.0.Beta3 Reporter: Tristan Tarrant Fix For: 8.0.0.Final Align the three server subsystems to use homogeneous projectCodes: JGroups: DGJGRP Infinispan: DGISPN Endpoint: DGENDPT -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5691?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5691: ---------------------------------- Status: Open (was: New) > 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, 1 month

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5691?page=com.atlassian.jira.plugin.... ] Work on ISPN-5691 started by Tristan Tarrant. --------------------------------------------- > 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, 1 month

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5691?page=com.atlassian.jira.plugin.... ] Work on ISPN-5691 stopped by Tristan Tarrant. --------------------------------------------- > 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, 1 month

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5691?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5691: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3666 > 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, 1 month

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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5692?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5692: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1238164 > 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 > > > {quote} > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=7 returned server error (status=0x85): org.infinispan.remoting.RemoteException: ISPN000217: Received exception from RemoteListenerWithDslFilterTest-NodeC-8427, see cause for remote stack trace > java.lang.ClassCastException: org.infinispan.query.remote.indexing.ProtobufValueWrapper cannot be cast to [B > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:336) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:126) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeaderOrEvent(Codec20.java:208) > at org.infinispan.client.hotrod.impl.operations.AddClientListenerOperation.executeOperation(AddClientListenerOperation.java:92) > at org.infinispan.client.hotrod.impl.operations.AddClientListenerOperation.executeOperation(AddClientListenerOperation.java:25) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:52) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.addClientListener(RemoteCacheImpl.java:575) > at org.infinispan.client.hotrod.event.ClientEvents.addClientQueryListener(ClientEvents.java:65) > at org.infinispan.client.hotrod.event.RemoteListenerWithDslFilterTest.testEventFilter(RemoteListenerWithDslFilterTest.java:144) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 August 2015