September 2018 - infinispan-issues

[JBoss JIRA] (ISPN-2069) Implement a caching servlet filter

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2069?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-2069. --------------------------------- Resolution: Won't Do > Implement a caching servlet filter > ---------------------------------- > > Key: ISPN-2069 > URL: https://issues.jboss.org/browse/ISPN-2069 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: NadirX > Priority: Minor > > Implement a servlet filter for caching web requests keyed on servlet path, parameters and headers. Look into support for web caching standards such as ESI. Possibly include a JSP tag library -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-1947. ----------------------------------- Resolution: Done > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 9.0.0.Beta1 > > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1823) Revisit internal collections used and replace with custom, high performance constructs

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1823?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1823. --------------------------------- Resolution: Out of Date > Revisit internal collections used and replace with custom, high performance constructs > -------------------------------------------------------------------------------------- > > Key: ISPN-1823 > URL: https://issues.jboss.org/browse/ISPN-1823 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.1.0.FINAL > Reporter: Manik Surtani > Priority: Minor > Labels: gc, memory, performance > > Most JDK collections are too inefficient for internal use, such as within contexts, cache transactions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1748) Allow consistency for concurrent updates when syncCommitPhase=false

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1748?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1748. --------------------------------- Resolution: Out of Date > Allow consistency for concurrent updates when syncCommitPhase=false > ------------------------------------------------------------------- > > Key: ISPN-1748 > URL: https://issues.jboss.org/browse/ISPN-1748 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Affects Versions: 5.1.0.CR4, 5.1.0.FINAL > Reporter: Mircea Markus > Priority: Optional > Labels: experimental, performance > Attachments: All_PUT.png > > > when syncCommitPhase=false then there is a window of inconsistency in the case multipel tx access the same key at the same time. > This can be avoided by sending the lock release command after the commit command, in the same thread which is async triggered by the TM.commit. > This should be a very important performance buster for default configurations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1548) Refactor API and Commons in self-contained packages to avoid package splitting issues

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1548?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1548. --------------------------------- Resolution: Out of Date > Refactor API and Commons in self-contained packages to avoid package splitting issues > ------------------------------------------------------------------------------------- > > Key: ISPN-1548 > URL: https://issues.jboss.org/browse/ISPN-1548 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 5.1.0.BETA5 > Reporter: NadirX > > With the split of core into api and commons (ISPN-1490) we have caused split packages (i.e. classes in the same package are split across multiple jars). This causes problems with OSGi (ISPN-1537) and will also be disallowed when signed jars will be made compulsory in EAP. > We therefore need to introduce new packages explicitly for api and commons. This will obviously have some impact on client code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1488) Document rehashWait configuration parameter

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1488?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1488. --------------------------------- Resolution: Out of Date > Document rehashWait configuration parameter > ------------------------------------------- > > Key: ISPN-1488 > URL: https://issues.jboss.org/browse/ISPN-1488 > Project: Infinispan > Issue Type: Feature Request > Components: Demos and Tutorials > Affects Versions: 5.1.0.BETA2 > Reporter: Michal Linhard > Priority: Minor > > http://docs.jboss.org/infinispan/5.1/apidocs/config.html#ce_clustering_hash > says > Future flag. Currenly unused. > but it's being used now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1414) Introduce a builder than can create an Infinispan CacheManager

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1414?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-1414. ----------------------------------- Resolution: Out of Date > Introduce a builder than can create an Infinispan CacheManager > -------------------------------------------------------------- > > Key: ISPN-1414 > URL: https://issues.jboss.org/browse/ISPN-1414 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Pete Muir > Assignee: Tristan Tarrant > > Provide a builder class that allows passing in of SPI instances, rather than doing lookup. This allows for much easier integration, as context from the app server bootstrap can be easily passed in. > For example: > {code} > public class CacheManagerBuilder { > void setClassLoader(ClassLoader cl); > void setTransport(Transport t); > ... > Cache start(); > } > {code} > We would still want to offer a wrapper around this for Java SE users that would expose a create a CacheManager easily. This factory would want to use a CacheManagerBuilder internally to create the cache, but offer a simplified API. You would want to expose the Builder from the factory as well, offering a sensible set of defaults for SE. > This would break backwards compatibility, as doing new EmbeddedCacheManager etc. would no longer be possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1307) REST protocol improvements for version 2

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1307?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-1307. ----------------------------------- Resolution: Out of Date The expiration part of this Jira has already been handled as part of other improvements > REST protocol improvements for version 2 > ---------------------------------------- > > Key: ISPN-1307 > URL: https://issues.jboss.org/browse/ISPN-1307 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: REST > > This JIRA is meant to act as an umbrella for improvements we might want to do in the REST protocol. For example: > - As shown in ISPN-1285 and https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+v..., the use of 0 as timeToLiveSeconds and/or maxIdleTimeSeconds parameter(s) is not very intuitive and it's not even symmetric. This should be sorted out. This has been highlighted again in ISPN-1425. One option could be to use -2 as @DefaultValue in order to distinguish between no values given and other options. > This JIRA should also figure out how to support multiple REST protocol versions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9510) NPE when running remote query operation with hotrod protocol 2.4

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9510?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9510: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6255 > NPE when running remote query operation with hotrod protocol 2.4 > ---------------------------------------------------------------- > > Key: ISPN-9510 > URL: https://issues.jboss.org/browse/ISPN-9510 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.0.CR2 > Reporter: Vittorio Rigamonti > Assignee: Gustavo Fernandes > > I have a query that runs with 9.3.1 and fails with 9.4.0.CR2 with NPE: > 15:22:40,145 DEBUG [org.infinispan.query.remote.impl.QueryFacadeImpl] (HotRod-ServerHandler-6-12) Error executing remote query : null: java.lang.NullPointerException > at org.infinispan.query.remote.impl.QuerySerializers.getSerializer(QuerySerializers.java:19) > at org.infinispan.query.remote.impl.BaseRemoteQueryManager.decodeQueryRequest(BaseRemoteQueryManager.java:63) > at org.infinispan.query.remote.impl.QueryFacadeImpl.query(QueryFacadeImpl.java:44) > at org.infinispan.server.hotrod.HotRodServer.query(HotRodServer.java:148) > at org.infinispan.server.hotrod.CacheRequestProcessor.queryInternal(CacheRequestProcessor.java:493) > at org.infinispan.server.hotrod.CacheRequestProcessor.lambda$query$31(CacheRequestProcessor.java:488) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) > at java.lang.Thread.run(Thread.java:748) > .proto model seems registered correctly > query is very simple: from sample_bank_account.User > using old hotrod 2.4 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1301) Check hashKeyMask of FIleCacheStore

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1301?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1301. --------------------------------- Resolution: Out of Date > Check hashKeyMask of FIleCacheStore > ----------------------------------- > > Key: ISPN-1301 > URL: https://issues.jboss.org/browse/ISPN-1301 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Loaders and Stores > Affects Versions: 5.0.0.CR8 > Reporter: Robert Stupp > > Related to ISPN-1300: > If the configured "hashKeyMask" value is changed for an existing cache store, the whole cache store becomes unusable. > Parts of the cache store configuration should be persisted in the file cache store and checked upon startup. > If the existing (persistent) configuration is different from what the user has set in the configuration XML (or programatically), two things are possible: > 1. print a WARNING that the cache store uses the persistent configuration > 2. like 1, but perform a re-hash of the file cache store, if a certain configuration option has been set -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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