August 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2033) JdbcBinaryCacheStore.purgeInternal() - releaseConnection() should be called in finally block.

by Jim Dunkerton (JIRA)

Jim Dunkerton created ISPN-2033: ----------------------------------- Summary: JdbcBinaryCacheStore.purgeInternal() - releaseConnection() should be called in finally block. Key: ISPN-2033 URL: https://issues.jboss.org/browse/ISPN-2033 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.1.2.FINAL Environment: JBoss 7.1.1 Final Reporter: Jim Dunkerton Assignee: Manik Surtani A potential memory leak of pooled DB connections is present in JdbcCacheBinaryStore. Observe the catch and finally blocks of the purgeInternal() method: catch (SQLException ex) { //if something happens make sure buckets locks are being release releaseLocks(expiredBuckets); connectionFactory.releaseConnection(conn); log.failedClearingJdbcCacheStore(ex); throw new CacheLoaderException("Failed clearing JdbcBinaryCacheStore", ex); } finally { JdbcUtil.safeClose(ps); JdbcUtil.safeClose(rs); } The pooled DB connection is not released unless an SQLException has been thrown. Contrast with JdbcStringBasedCacheStore.purgeInternal(): } catch (SQLException ex) { log.failedClearingJdbcCacheStore(ex); throw new CacheLoaderException("Failed clearing string based JDBC store", ex); } finally { JdbcUtil.safeClose(ps); connectionFactory.releaseConnection(conn); } When using a JdbcMixedCacheStore, I noticed a DB connection leak. It appeared that for every two connections being acquired, only one was being released. I believe it is down to the fact that the JdbcBinaryCacheStore inside the JdbcMixedCacheStore is not releasing its connections properly (i.e. in its finally block) whereas the JdbcStringBasedCacheStore is. I guess a workaround is to use only a JdbcStringBasedCacheStore, not a JdbcMixedCacheStore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
10
0 / 0

[JBoss JIRA] Created: (ISPN-503) collate keys in replication queue

by Mircea Markus (JIRA)

collate keys in replication queue ---------------------------------- Key: ISPN-503 URL: https://jira.jboss.org/browse/ISPN-503 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 4.1.0.BETA2 Reporter: Mircea Markus Assignee: Manik Surtani At the moment the replication queue is replicating all the keys. What it can do is to collate them, similar to the way cache stores are collating writes. E.g. 1. put(k,v1) 2. put(k,v2). This can be collated in put(k,v2), as put(k,v1) is redundant. This would optimize async replication in a way that cannot be handled by jgroups. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (ISPN-159) Extended coalesced logic to other parts

by Galder Zamarreno (JIRA)

Extended coalesced logic to other parts --------------------------------------- Key: ISPN-159 URL: https://jira.jboss.org/jira/browse/ISPN-159 Project: Infinispan Issue Type: Feature Request Components: RPC, Transactions Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR1 Reuse same coalesced async cache store logic to: - Reduce size of replicable commands where N modifications are sent so that only latest state is sent. - Manage the async replication queue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (ISPN-330) Separate scheduled/unscheduled async cache store configuration

by Galder Zamarreno (JIRA)

Separate scheduled/unscheduled async cache store configuration -------------------------------------------------------------- Key: ISPN-330 URL: https://jira.jboss.org/jira/browse/ISPN-330 Project: Infinispan Issue Type: Sub-task Components: Configuration, Loaders and Stores Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Implement configuration that allows differentiation between scheduled/unscheduled strategies: <async enabled="true"> <scheduled frequency="1000" /> </async> <async enabled="true"> <unscheduled poolsize="50" /> </async> This format allows for easier extension of properties in scheduled/unscheduled modes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] (ISPN-2181) Allow to inject the current cache into Mapper/Reducer/Callable objects

by Nicolas Filotto (JIRA)

Nicolas Filotto created ISPN-2181: ------------------------------------- Summary: Allow to inject the current cache into Mapper/Reducer/Callable objects Key: ISPN-2181 URL: https://issues.jboss.org/browse/ISPN-2181 Project: Infinispan Issue Type: Enhancement Components: CDI integration Affects Versions: 5.2.0.ALPHA2 Reporter: Nicolas Filotto Assignee: Pete Muir Thanks to ISPN-1636, it is now possible to inject the cache into Mapper/Reducer/Callable objects however the cache injected is the default cache not the cache for which the MapReduceTask/DistributedExecutorService has been created which is quite error prone since we don't expect to get the default cache but the current cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

6
17
0 / 0

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2203: -------------------------------------- Summary: Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable Key: ISPN-2203 URL: https://issues.jboss.org/browse/ISPN-2203 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Tomas Sykora Fix For: 5.2.0.ALPHA3 Test being disabled as part of ISPN-2196 cos it's unstable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
7
0 / 0

[JBoss JIRA] (ISPN-2249) Fix test failures introduced with NBST

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2249: ----------------------------------- Summary: Fix test failures introduced with NBST Key: ISPN-2249 URL: https://issues.jboss.org/browse/ISPN-2249 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.0.Alpha3 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.Alpha4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
18
0 / 0

[JBoss JIRA] (ISPN-1842) Configuration schema is not included at expected location

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1842: ------------------------------------- Summary: Configuration schema is not included at expected location Key: ISPN-1842 URL: https://issues.jboss.org/browse/ISPN-1842 Project: Infinispan Issue Type: Bug Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL Just found these messages in my logs: {quote} 17:04:43,731 (main) DEBUG FileLookup:57 - Unable to find file schema/infinispan-config-5.1.xsd in classpath; searching for this file on the filesystem instead. 17:04:43,731 (main) DEBUG InfinispanConfiguration:389 - Could not find schema on path schema/infinispan-config-5.1.xsd, resolving infinispan.config.schema to http://www.infinispan.org/schemas/infinispan-config-5.1.xsd 17:04:43,911 (main) DEBUG InfinispanConfiguration:396 - Using schema http://www.infinispan.org/schemas/infinispan-config-5.1.xsd {quote} Indeed the schema is included in the jar, but is in the root of the jar, while it's searched for in *schema/infinispan-config-5.1.xsd* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
13
0 / 0

[JBoss JIRA] Created: (ISPN-1103) Soft schema-based storage

by Manik Surtani (JIRA)

Soft schema-based storage ------------------------- Key: ISPN-1103 URL: https://issues.jboss.org/browse/ISPN-1103 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final This JIRA is about storing metadata alongside values. Perhaps encapsulating values as SchematicValues, which could be described as: {code} class SchematicValue { String jsonMetadata; String jsonObject; } {code} Metadata would allow for a few interesting features: * Extracting of lifespan and timestamp data if manipulated over a remote protocol (REST, HotRod, etc) * Content type for REST responses * Timestamps for REST headers, will affect HTTP content caches * Validation information (may not be processed by Infinispan, but can be used by client libs) * Classloader/marshaller/classdef version info * General structure of the information stored -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

8
22
0 / 0

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

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2069: ------------------------------------- Summary: Implement a caching servlet filter Key: ISPN-2069 URL: https://issues.jboss.org/browse/ISPN-2069 Project: Infinispan Issue Type: Feature Request Reporter: Tristan Tarrant Assignee: Tristan Tarrant 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2012