April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2

by Mikhail Dobrinin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Mikhail Dobrinin commented on ISPN-3076: ---------------------------------------- Any chance for this to get finished? Log4j2 should be supported by jboss-logging as of 3.2.1 - JBLOGGING-112. > Infinispan should enable use of log4j2 > -------------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 5.2.5.Final, 6.0.0.Final > Environment: Any > Reporter: Divya Mehra > > log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing > 1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar). > Also refer: https://issues.jboss.org/browse/ISPN-2976 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5019) After coordinator change, cache topologies should be installed in parallel

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5019?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5019: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1195565|https://bugzilla.redhat.com/show_bug.cgi?id=1195565] from POST to MODIFIED > After coordinator change, cache topologies should be installed in parallel > -------------------------------------------------------------------------- > > Key: ISPN-5019 > URL: https://issues.jboss.org/browse/ISPN-5019 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.CR1, 7.2.0.Final > > > When the coordinator crashes, the new coordinator has to recover the cache topologies from all the nodes in the cluster and install updated topologies for all the caches. This is done on a single thread, and it can take a long time when there are a lot of caches. > We should be accelerate this by doing the topology installation on separate threads. However, we have to be careful with the async transport pool, because {{executeOnClusterAsync}} actually needs to spawn a new thread in the same pool. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5388?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5388: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1211944 > Optimize redundant predicates (non-indexed query) > ------------------------------------------------- > > Key: ISPN-5388 > URL: https://issues.jboss.org/browse/ISPN-5388 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: > * X || X => X > * X && X => X > * !X || !X => !X > * !X && !X => !X > * X || !X => TRUE (tautology) > * X && !X => FALSE (contradiction) > (where X is a predicate not a general boolean expression) > Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5380) Create a registry of internal caches

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5380?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5380: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Create a registry of internal caches > ------------------------------------ > > Key: ISPN-5380 > URL: https://issues.jboss.org/browse/ISPN-5380 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.Final > > > Several parts of the code create caches for internal use (hotrod topology, protobuf schema, scripting cache, recovery, etc). These should all be created through a common interface so that thet can be filtered out when necessary. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5381) CacheContainerStats returns negative number of stores

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5381?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5381: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > CacheContainerStats returns negative number of stores > ----------------------------------------------------- > > Key: ISPN-5381 > URL: https://issues.jboss.org/browse/ISPN-5381 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 7.2.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.Final > > > CacheContainerStatsImpl adds stores from caches with disabled statistics and returns negative numbers -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5382) Enable scripting in server distribution

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5382?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5382: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Enable scripting in server distribution > --------------------------------------- > > Key: ISPN-5382 > URL: https://issues.jboss.org/browse/ISPN-5382 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 7.2.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.Final > > > Include the scripting module in the infinispan subsystem -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5390) QueryCache should use the internal cache registry

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5390: ----------------------------------- Summary: QueryCache should use the internal cache registry Key: ISPN-5390 URL: https://issues.jboss.org/browse/ISPN-5390 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying Affects Versions: 7.2.0.Beta2 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.2.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5390) QueryCache should use the internal cache registry

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5390?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5390: -------------------------------- Status: Open (was: New) > QueryCache should use the internal cache registry > ------------------------------------------------- > > Key: ISPN-5390 > URL: https://issues.jboss.org/browse/ISPN-5390 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5388) Optimize redundant predicates (non-indexed query)

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5388?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5388: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Optimize redundant predicates (non-indexed query) > ------------------------------------------------- > > Key: ISPN-5388 > URL: https://issues.jboss.org/browse/ISPN-5388 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > Cases where predicates evaluate to constant values are already detected and handled. But besides such trivial simplifications we should also try to handle more advanced simplification rules like: > * X || X => X > * X && X => X > * !X || !X => !X > * !X && !X => !X > * X || !X => TRUE (tautology) > * X && !X => FALSE (contradiction) > (where X is a predicate not a general boolean expression) > Even further simplification could be achieved if we were able to handle the general case where X is a general boolean expression, but we'll not try that yet for the sake of complexity. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5347) Extend org.infinispan.objectfilter.Matcher to support event types and user context data

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5347?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5347: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Extend org.infinispan.objectfilter.Matcher to support event types and user context data > --------------------------------------------------------------------------------------- > > Key: ISPN-5347 > URL: https://issues.jboss.org/browse/ISPN-5347 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > The Matcher should accept a user context object and an event type object beside the instance being tested and should pass the user context and event type to the callback of the matching subscriptions. The user context object and event type should be optional. > Also, when subscribing the user should be able to specify an optional event type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015