July 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9295) Server fails to start if maven repo does not have Xerces

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/ISPN-9295?page=com.atlassian.jira.plugin.... ] James Livingston commented on ISPN-9295: ---------------------------------------- Was not shipping all the jars in the infinispan-server-build artifact in maven a problem (so it will have them all for 9.3.1 or 9.4), or by design and they won't in future either? > Server fails to start if maven repo does not have Xerces > -------------------------------------------------------- > > Key: ISPN-9295 > URL: https://issues.jboss.org/browse/ISPN-9295 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.3.0.CR1 > Reporter: Galder Zamarreño > Priority: Minor > Fix For: 9.3.0.Final > > > If XercesImpl is not present in maven repo, there doesn't seem to be an attempt to download and instead you get: > {code} > [Host Controller] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP5' (position: END_TAG seen ...resources>\n <artifact name="xerces:xercesImpl:2.11.0.SP5"/>... @26:56) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:981) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:869) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:659) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:426) > [Host Controller] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:302) > [Host Controller] ... 15 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9370) Always consult CacheLoader if entry is not in data container

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9370?page=com.atlassian.jira.plugin.... ] Work on ISPN-9370 started by William Burns. ------------------------------------------- > Always consult CacheLoader if entry is not in data container > ------------------------------------------------------------ > > Key: ISPN-9370 > URL: https://issues.jboss.org/browse/ISPN-9370 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.3.1.Final > > > Currently we do not query the underlying persistence layer when an entry was found to be expired in memory. However it makes sense to query a CacheLoader (that is that it doesn't implement CacheStore) even when an entry is expired. This allows for users to configure a CacheLoader that always returns non null and the cache will never return null. > Please see https://github.com/infinispan/infinispan/pull/6071 more information -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9370) Always consult CacheLoader if entry is not in data container

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9370?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9370: -------------------------------- Status: Open (was: New) > Always consult CacheLoader if entry is not in data container > ------------------------------------------------------------ > > Key: ISPN-9370 > URL: https://issues.jboss.org/browse/ISPN-9370 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Alpha1, 9.3.1.Final > > > Currently we do not query the underlying persistence layer when an entry was found to be expired in memory. However it makes sense to query a CacheLoader (that is that it doesn't implement CacheStore) even when an entry is expired. This allows for users to configure a CacheLoader that always returns non null and the cache will never return null. > Please see https://github.com/infinispan/infinispan/pull/6071 more information -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9370) Always consult CacheLoader if entry is not in data container

by William Burns (JIRA)

William Burns created ISPN-9370: ----------------------------------- Summary: Always consult CacheLoader if entry is not in data container Key: ISPN-9370 URL: https://issues.jboss.org/browse/ISPN-9370 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Reporter: William Burns Assignee: William Burns Fix For: 9.4.0.Alpha1, 9.3.1.Final Currently we do not query the underlying persistence layer when an entry was found to be expired in memory. However it makes sense to query a CacheLoader (that is that it doesn't implement CacheStore) even when an entry is expired. This allows for users to configure a CacheLoader that always returns non null and the cache will never return null. Please see https://github.com/infinispan/infinispan/pull/6071 more information -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6728) Add ability to override maxClauseCount

by Arnav Bhati (JIRA)

[ https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin.... ] Arnav Bhati edited comment on ISPN-6728 at 7/12/18 10:34 AM: ------------------------------------------------------------- [~anistor] - can you confirm if below is correct ? public void setQueryMaxClauses(int queryMaxClauses) { this.queryMaxClauses = queryMaxClauses; BooleanQuery.setMaxClauseCount(this.queryMaxClauses); } was (Author: rhn-support-abhati): [~anistor] - can you provide a sample for such script ? > Add ability to override maxClauseCount > --------------------------------------- > > Key: ISPN-6728 > URL: https://issues.jboss.org/browse/ISPN-6728 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying, Server > Reporter: Van Halbert > Assignee: Adrian Nistor > Priority: Minor > > We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message: > - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting > This will occur when there are more than 1024 "IN" conditions specified on the query builder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6728) Add ability to override maxClauseCount

by Arnav Bhati (JIRA)

[ https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin.... ] Arnav Bhati commented on ISPN-6728: ----------------------------------- [~anistor] - can you provide a sample for such script ? > Add ability to override maxClauseCount > --------------------------------------- > > Key: ISPN-6728 > URL: https://issues.jboss.org/browse/ISPN-6728 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying, Server > Reporter: Van Halbert > Assignee: Adrian Nistor > Priority: Minor > > We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message: > - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting > This will occur when there are more than 1024 "IN" conditions specified on the query builder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6728) Add ability to override maxClauseCount

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6728: ------------------------------------- Another possible workaround is to execute a script or server task that invokes BooleanQuery.setMaxClauseCount setting a higher value. There is however a slight chance that will not work as expected because a different classloader might be used for query module than for the executing task, so the static field being set does not affect the value seen by query module, but it is still worth trying it. I haven't yet, so cannot confirm it's a sure workaround. > Add ability to override maxClauseCount > --------------------------------------- > > Key: ISPN-6728 > URL: https://issues.jboss.org/browse/ISPN-6728 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying, Server > Reporter: Van Halbert > Priority: Minor > > We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message: > - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting > This will occur when there are more than 1024 "IN" conditions specified on the query builder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6728) Add ability to override maxClauseCount

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-6728: ----------------------------------- Assignee: Adrian Nistor > Add ability to override maxClauseCount > --------------------------------------- > > Key: ISPN-6728 > URL: https://issues.jboss.org/browse/ISPN-6728 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying, Server > Reporter: Van Halbert > Assignee: Adrian Nistor > Priority: Minor > > We are using the Hotrod client, and need the ability to specify or override the maxClauseCount setting, otherwise, we get the following error message: > - org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024 setting > This will occur when there are more than 1024 "IN" conditions specified on the query builder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9369) Non transactional query cache only cache results if transaction is committed

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9369: -------------------------------------- Summary: Non transactional query cache only cache results if transaction is committed Key: ISPN-9369 URL: https://issues.jboss.org/browse/ISPN-9369 Project: Infinispan Issue Type: Bug Components: Hibernate Cache Affects Versions: 9.3.0.Final Reporter: Galder Zamarreño {quote}Local query caches are not populated if the transaction is not committed. The same test case works on hibernate 4.3.11 Our scenario: Read-only services that only execute queries and never commit the transaction. It should still be possible to use/configure hibernate/infinispan to cache the results, regardless the transaction state.{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8023) Make Hibernate Cache produce OSGI bundles

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8023?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8023: ----------------------------------- Status: Open (was: New) > Make Hibernate Cache produce OSGI bundles > ----------------------------------------- > > Key: ISPN-8023 > URL: https://issues.jboss.org/browse/ISPN-8023 > Project: Infinispan > Issue Type: Enhancement > Components: Hibernate Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.4.0.Alpha1, 9.4.0.Final > > > Make the hibernate-cache pom.xml produce OSGI bundles. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 2018