November 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5905) Avoid creating a FilterEvalContext for non-matching subscriptions

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5905?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5905: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3800 > Avoid creating a FilterEvalContext for non-matching subscriptions > ----------------------------------------------------------------- > > Key: ISPN-5905 > URL: https://issues.jboss.org/browse/ISPN-5905 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.0.2.Final > > > MatcherEvalContext.getFilterEvalContext crates a FilterEvalContext on the fly. > So during the dispatching of notifications all FilterEvalContexts get created, even for non-matching subscriptions. This can be easily avoided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5905) Avoid creating a FilterEvalContext for non-matching subscriptions

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5905?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5905: -------------------------------- Fix Version/s: 8.0.2.Final > Avoid creating a FilterEvalContext for non-matching subscriptions > ----------------------------------------------------------------- > > Key: ISPN-5905 > URL: https://issues.jboss.org/browse/ISPN-5905 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.0.2.Final > > > MatcherEvalContext.getFilterEvalContext crates a FilterEvalContext on the fly. > So during the dispatching of notifications all FilterEvalContexts get created, even for non-matching subscriptions. This can be easily avoided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5906) Hide implementation details from package org.infinispan.query.continuous

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5906: ----------------------------------- Summary: Hide implementation details from package org.infinispan.query.continuous Key: ISPN-5906 URL: https://issues.jboss.org/browse/ISPN-5906 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying Affects Versions: 8.1.0.Alpha2 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.1.0.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5906) Hide implementation details from package org.infinispan.query.continuous

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5906?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5906: -------------------------------- Status: Open (was: New) > Hide implementation details from package org.infinispan.query.continuous > ------------------------------------------------------------------------ > > Key: ISPN-5906 > URL: https://issues.jboss.org/browse/ISPN-5906 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5905) Avoid creating a FilterEvalContext for non-matching subscriptions

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5905?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5905: -------------------------------- Status: Open (was: New) > Avoid creating a FilterEvalContext for non-matching subscriptions > ----------------------------------------------------------------- > > Key: ISPN-5905 > URL: https://issues.jboss.org/browse/ISPN-5905 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1 > > > MatcherEvalContext.getFilterEvalContext crates a FilterEvalContext on the fly. > So during the dispatching of notifications all FilterEvalContexts get created, even for non-matching subscriptions. This can be easily avoided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5831) Create cache container level operations for managing state transfer

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5831?page=com.atlassian.jira.plugin.... ] Pedro Zapata closed ISPN-5831. ------------------------------ Resolution: Duplicate Issue > Create cache container level operations for managing state transfer > ------------------------------------------------------------------- > > Key: ISPN-5831 > URL: https://issues.jboss.org/browse/ISPN-5831 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Pedro Zapata > Assignee: Tristan Tarrant > Labels: jdg7 > > We need cache container level operations bringing sites online/offline and managing state transfer operations. > Currently, this operations are cache based but we are interested in the management console UI to perform them at the cache container level. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5905) Avoid creating a FilterEvalContext for non-matching subscriptions

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5905: ----------------------------------- Summary: Avoid creating a FilterEvalContext for non-matching subscriptions Key: ISPN-5905 URL: https://issues.jboss.org/browse/ISPN-5905 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying Affects Versions: 8.1.0.Alpha2 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.1.0.Beta1 MatcherEvalContext.getFilterEvalContext crates a FilterEvalContext on the fly. So during the dispatching of notifications all FilterEvalContexts get created, even for non-matching subscriptions. This can be easily avoided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5467?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5467: ------------------------------- Status: Open (was: New) > Design new interceptor interfaces for sequential invocation > ----------------------------------------------------------- > > Key: ISPN-5467 > URL: https://issues.jboss.org/browse/ISPN-5467 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.1.0.Final > > > We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5467?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-5467: ---------------------------------- Assignee: Dan Berindei > Design new interceptor interfaces for sequential invocation > ----------------------------------------------------------- > > Key: ISPN-5467 > URL: https://issues.jboss.org/browse/ISPN-5467 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Final > > > We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5613) Replication timeouts should show more information of the affected entries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5613?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5613: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1243953|https://bugzilla.redhat.com/show_bug.cgi?id=1243953] from ASSIGNED to POST > Replication timeouts should show more information of the affected entries > ------------------------------------------------------------------------- > > Key: ISPN-5613 > URL: https://issues.jboss.org/browse/ISPN-5613 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > > Typical timeouts for replication are > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (remote-thread-595) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Replication timeout for jboss####-##### > and > ERROR .... > Caused by: org.infinispan.util.concurrent.TimeoutException: Node jboss####-##### timed out > The issue is that it is not possible to check what key/entry is affected. > The cache can become inconsistent between nodes. > There should be an information which key is affected. > For some operations it is not possible at all as there is no information about the entries (i.e. commit) or the key is binary or custom without a valid toString() method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2015