July 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2849) Don't keep threads blocked when waiting for locks to be released

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2849?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-2849: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3606 > Don't keep threads blocked when waiting for locks to be released > ---------------------------------------------------------------- > > Key: ISPN-2849 > URL: https://issues.jboss.org/browse/ISPN-2849 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Fix For: 8.0.0.Beta2 > > > ATM if a tx2 waits on a lock to be released by tx1, the (incoming) tx2 thread is BLOCKED and taken out from the pool. A better way to implement this is by using a structure that would hold and order the depending transactions on the receiver correlated with the async execution API from JGroups 3.3.0, result being that tx2 would not BLOCK but return to the pool this (not maxing out the thread pool that executes commands). > More about it in the "Async invocation section" of https://docspace.corp.redhat.com/docs/DOC-134411 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5626) Clean up missing parts for Distributed Streams

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5626?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5626: -------------------------------- Description: There are some things left over that need to still be done possibly # Investigate iterator parallel stream performance # Add support for key filter applying to cache loader # Add cache loader managed blocker # Add tests for skip & limit. # Add tests for containsValue requiring serialization overhead. # Change isEmpty to use findAny # Need to test a map/flatMap operation after an intermediate terminal operation such as sorted. This is to verify the iterator doesn't use the different map operation. # Add timeout for remote operations to be equal to replication sync timeout # Add new BitSetSet support to reduce segments footprint # Support concurrent activations properly (this is also an issue with state transfer) was: There are some things left over that need to still be done possibly # Investigate iterator parallel stream performance # Add support for key filter applying to cache loader # Add cache loader managed blocker # Add tests for skip & limit. # Add tests for containsValue requiring serialization overhead. # Change isEmpty to use findAny # Need to test a map/flatMap operation after an intermediate terminal operation such as sorted. This is to verify the iterator doesn't use the different map operation. # Add timeout for remote operations to be equal to replication sync timeout # Add new BitSetSet support to reduce segments footprint > Clean up missing parts for Distributed Streams > ---------------------------------------------- > > Key: ISPN-5626 > URL: https://issues.jboss.org/browse/ISPN-5626 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > > There are some things left over that need to still be done possibly > # Investigate iterator parallel stream performance > # Add support for key filter applying to cache loader > # Add cache loader managed blocker > # Add tests for skip & limit. > # Add tests for containsValue requiring serialization overhead. > # Change isEmpty to use findAny > # Need to test a map/flatMap operation after an intermediate terminal operation such as sorted. This is to verify the iterator doesn't use the different map operation. > # Add timeout for remote operations to be equal to replication sync timeout > # Add new BitSetSet support to reduce segments footprint > # Support concurrent activations properly (this is also an issue with state transfer) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2976) Log4J dependencies in codebase to be cleaned up

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2976?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-2976. -------------------------------- Labels: (was: core) Assignee: Tristan Tarrant Fix Version/s: 8.0.0.Beta2 Resolution: Done The dependencies in SampleConfigFilesCorrectnessTest, CompressedFileAppender, and ThreadNameFilter are required, but were updated to the log4j 2.0 SPI. > Log4J dependencies in codebase to be cleaned up > ----------------------------------------------- > > Key: ISPN-2976 > URL: https://issues.jboss.org/browse/ISPN-2976 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 5.2.5.Final > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Fix For: 8.0.0.Beta2 > > > When attempting to move to Log4J 2.0, I've noticed a number of hard deps on log4j classes. > {{SampleConfigFilesCorrectnessTest}} - this class makes use of a custom appender to analyse what a user is being warned of when a config file is parsed. Why are we using Log4J for this? Our own logging interface should be mocked and messages captured directly. > {{RehashStressTest}} and {{NucleotideCache}} - seems like a bug, I presume the author intended to use {{org.infinispan.logging.Log}}. > {{CompressedFileAppender}} and {{ThreadNameFilter}}- can this be written in a way that works with Log4J 1.x as well as 2.x? Or have the SPIs changed that much? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5626) Clean up missing parts for Distributed Streams

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5626?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5626: -------------------------------- Description: There are some things left over that need to still be done possibly # Investigate iterator parallel stream performance # Add support for key filter applying to cache loader # Add cache loader managed blocker # Add tests for skip & limit. # Add tests for containsValue requiring serialization overhead. # Change isEmpty to use findAny # Need to test a map/flatMap operation after an intermediate terminal operation such as sorted. This is to verify the iterator doesn't use the different map operation. # Add timeout for remote operations to be equal to replication sync timeout # Add new BitSetSet support to reduce segments footprint was: There are some things left over that need to still be done possibly # Investigate iterator parallel stream performance # Add support for key filter applying to cache loader # Add cache loader managed blocker # Add tests for skip & limit. # Add tests for containsValue requiring serialization overhead. # Change isEmpty to use findAny # Need to test a map/flatMap operation after an intermediate terminal operation such as sorted. This is to verify the iterator doesn't use the different map operation. # Add timeout to iterator to be equal to state transfer timeout. # Add new BitSetSet support to reduce segments footprint > Clean up missing parts for Distributed Streams > ---------------------------------------------- > > Key: ISPN-5626 > URL: https://issues.jboss.org/browse/ISPN-5626 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > > There are some things left over that need to still be done possibly > # Investigate iterator parallel stream performance > # Add support for key filter applying to cache loader > # Add cache loader managed blocker > # Add tests for skip & limit. > # Add tests for containsValue requiring serialization overhead. > # Change isEmpty to use findAny > # Need to test a map/flatMap operation after an intermediate terminal operation such as sorted. This is to verify the iterator doesn't use the different map operation. > # Add timeout for remote operations to be equal to replication sync timeout > # Add new BitSetSet support to reduce segments footprint -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3076: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 > Assignee: Tristan Tarrant > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > 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.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5632) Address rework comments for ISPN-5293

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5632?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5632: -------------------------------- Parent: ISPN-5626 Issue Type: Sub-task (was: Bug) > Address rework comments for ISPN-5293 > ------------------------------------- > > Key: ISPN-5632 > URL: https://issues.jboss.org/browse/ISPN-5632 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: William Burns > Assignee: William Burns > > There are some new rework comments for https://github.com/infinispan/infinispan/pull/3569. This issue will cover those. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5633) Upgrade console to 8.0.0.Beta1

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5633?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5633: ---------------------------------- Status: Open (was: New) > Upgrade console to 8.0.0.Beta1 > ------------------------------ > > Key: ISPN-5633 > URL: https://issues.jboss.org/browse/ISPN-5633 > Project: Infinispan > Issue Type: Component Upgrade > Components: Console > Affects Versions: 8.0.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5633) Upgrade console to 8.0.0.Beta1

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5633?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5633: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3605/files > Upgrade console to 8.0.0.Beta1 > ------------------------------ > > Key: ISPN-5633 > URL: https://issues.jboss.org/browse/ISPN-5633 > Project: Infinispan > Issue Type: Component Upgrade > Components: Console > Affects Versions: 8.0.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5633) Upgrade console to 8.0.0.Beta1

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5633: ------------------------------------- Summary: Upgrade console to 8.0.0.Beta1 Key: ISPN-5633 URL: https://issues.jboss.org/browse/ISPN-5633 Project: Infinispan Issue Type: Component Upgrade Components: Console Affects Versions: 8.0.0.Beta1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 8.0.0.Beta2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5561) Problem in dealing with the HQL queries that contain string comparison operations, when it involves empty string as an operand

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5561?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5561: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1238866|https://bugzilla.redhat.com/show_bug.cgi?id=1238866] from MODIFIED to POST > Problem in dealing with the HQL queries that contain string comparison operations, when it involves empty string as an operand > ------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-5561 > URL: https://issues.jboss.org/browse/ISPN-5561 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 7.2.0.Final > Environment: Infinispan version: Infinispan 7.2.0-Final > Operating System: Linux > Compatibility mode is enabled. > Indexing is enabled and 'autoconfig' parameter is set to true. > Reporter: Pavan Kundgol > Assignee: Adrian Nistor > Fix For: 8.0.0.Beta2, 7.2.4.Final, 8.0.0.Final > > > When a HQL query that involves string comparison operation with the empty string matching is executed through hot rod client(java), it is resulting in the following error, > org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[7] returned server error (status=0x85): org.hibernate.search.exception.EmptyQueryException: HSEARCH000146: The query string '' applied on field 'CITY' has no meaningful tokens to be matched. Validate the query input against the Analyzer applied on this field. > The same problem may also occur when the string matching operation involves a string containing certain special keywords(hibernate search stop words), as operands. > The problem seems to be assosiated with the the 'hibernate-hql-lucene' parser used by the 'infinispan-remote-query-server' module. The problem here is that the hibernate-hql-lucene parser is translating comparison operations directly into lucene keyword matching operations, irrespective of the field type, though the phrase matching is more appropriate for string fields. This leads to invalid query formation when the field in concern is of type string, and is matched against an empty string(or a string containing one or more hibernate search stop words). > For example, > the where condition city='' present in the following HQL query > select name from com.test.User where city='' > is tralated to lucene query, the hql-lucene parser is currently translating to > queryBuilder.keyword().onField("city").matching("").createQuery() > whereas recommended one is > queryBuilder.phrase().onField("city").sentence("").createQuery() > In the former way of translation, Hibernate Search query execution fails due to its usage of standard analyzer while executing the query. Hence, the problem can also be avoided by disabling the standard analyzer while executing the query. > queryBuilder.keyword().onField("city").ignoreAnalyzer().matching("").createQuery() > Preferred solution may be to enhance the 'hibernate-hql-lucene' library to do type specific translations, and to specifically translate the string comparison operations of hql query into phrase matching operations of lucene query(instead of keyword matching operations). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 July 2015