June 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5527) Java system properties no longer supported in leveldb expiration path

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5527?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5527: ---------------------------------- Fix Version/s: 8.0.0.Alpha2 7.2.3.Final 8.0.0.Final > Java system properties no longer supported in leveldb expiration path > --------------------------------------------------------------------- > > Key: ISPN-5527 > URL: https://issues.jboss.org/browse/ISPN-5527 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.2.0.Final > Reporter: Paul Richardson > Assignee: Tristan Tarrant > Fix For: 8.0.0.Alpha2, 7.2.3.Final, 8.0.0.Final > > > In 6.0, it was possible to create a leveldb cache configuration like: > {code} > <leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" > location="${user.home}/.komodo/db/data" > expiredLocation="${user.home}/.komodo/db/expired" > implementationType="JAVA"> > </leveldbStore> > {code} > Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute: > {code} > <leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" > path="${user.home}/.komodo/db/data"> > <expiration path="${user.home}/.komodo/db/expired"/> > <implementation type="JAVA"/> > </leveldb-store> > {code} > Looking at the [LevelDBStoreConfigurationParser72|https://github.com/infinispan/infinispa...] class, the method parseLevelDBCacheStore() (line 55) has a call to: > {code} > String value = StringPropertyReplacer.replaceProperties(attributeValue); > {code} > while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5527) Java system properties no longer supported in leveldb expiration path

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5527?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5527: ---------------------------------- Status: Open (was: New) > Java system properties no longer supported in leveldb expiration path > --------------------------------------------------------------------- > > Key: ISPN-5527 > URL: https://issues.jboss.org/browse/ISPN-5527 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.2.0.Final > Reporter: Paul Richardson > Fix For: 8.0.0.Alpha2, 7.2.3.Final, 8.0.0.Final > > > In 6.0, it was possible to create a leveldb cache configuration like: > {code} > <leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" > location="${user.home}/.komodo/db/data" > expiredLocation="${user.home}/.komodo/db/expired" > implementationType="JAVA"> > </leveldbStore> > {code} > Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute: > {code} > <leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" > path="${user.home}/.komodo/db/data"> > <expiration path="${user.home}/.komodo/db/expired"/> > <implementation type="JAVA"/> > </leveldb-store> > {code} > Looking at the [LevelDBStoreConfigurationParser72|https://github.com/infinispan/infinispa...] class, the method parseLevelDBCacheStore() (line 55) has a call to: > {code} > String value = StringPropertyReplacer.replaceProperties(attributeValue); > {code} > while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5527) Java system properties no longer supported in leveldb expiration path

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5527?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-5527: ------------------------------------- Assignee: Tristan Tarrant > Java system properties no longer supported in leveldb expiration path > --------------------------------------------------------------------- > > Key: ISPN-5527 > URL: https://issues.jboss.org/browse/ISPN-5527 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.2.0.Final > Reporter: Paul Richardson > Assignee: Tristan Tarrant > Fix For: 8.0.0.Alpha2, 7.2.3.Final, 8.0.0.Final > > > In 6.0, it was possible to create a leveldb cache configuration like: > {code} > <leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" > location="${user.home}/.komodo/db/data" > expiredLocation="${user.home}/.komodo/db/expired" > implementationType="JAVA"> > </leveldbStore> > {code} > Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute: > {code} > <leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" > path="${user.home}/.komodo/db/data"> > <expiration path="${user.home}/.komodo/db/expired"/> > <implementation type="JAVA"/> > </leveldb-store> > {code} > Looking at the [LevelDBStoreConfigurationParser72|https://github.com/infinispan/infinispa...] class, the method parseLevelDBCacheStore() (line 55) has a call to: > {code} > String value = StringPropertyReplacer.replaceProperties(attributeValue); > {code} > while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5527) Java system properties no longer supported in leveldb expiration path

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5527?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5527: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3526, https://github.com/infinispan/infinispan/pull/3527 > Java system properties no longer supported in leveldb expiration path > --------------------------------------------------------------------- > > Key: ISPN-5527 > URL: https://issues.jboss.org/browse/ISPN-5527 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.2.0.Final > Reporter: Paul Richardson > Assignee: Tristan Tarrant > Fix For: 8.0.0.Alpha2, 7.2.3.Final, 8.0.0.Final > > > In 6.0, it was possible to create a leveldb cache configuration like: > {code} > <leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" > location="${user.home}/.komodo/db/data" > expiredLocation="${user.home}/.komodo/db/expired" > implementationType="JAVA"> > </leveldbStore> > {code} > Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute: > {code} > <leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" > path="${user.home}/.komodo/db/data"> > <expiration path="${user.home}/.komodo/db/expired"/> > <implementation type="JAVA"/> > </leveldb-store> > {code} > Looking at the [LevelDBStoreConfigurationParser72|https://github.com/infinispan/infinispa...] class, the method parseLevelDBCacheStore() (line 55) has a call to: > {code} > String value = StringPropertyReplacer.replaceProperties(attributeValue); > {code} > while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5524) Race condition in SemaphoreCompletionService.executeFront()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5524?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5524: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1229181|https://bugzilla.redhat.com/show_bug.cgi?id=1229181] from NEW to ASSIGNED > Race condition in SemaphoreCompletionService.executeFront() > ----------------------------------------------------------- > > Key: ISPN-5524 > URL: https://issues.jboss.org/browse/ISPN-5524 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.0.0.Alpha2, 7.2.3.Final > > > If two threads call {{executeFront()}} at the same time, it's possible that none of them executes any task, although there are permits available, and one of the threads just added a task in the queue. This scenario causes random initial state transfer timeouts in the testsuite: > # T1: continueTaskInBackground(): queue = empty, permits = 0 > # T1: backgroundTaskFinished() > # T1: = semaphore.release(): queue = empty, permits = 1 > # T1: = executeFront() > # T1: == semaphore.acquire() -> true: queue = empty, permits = 0 > # T2: == queue.poll() -> null > # T2: submit(task) > # T2: = executeFront() > # T2: == semaphore.acquire() -> false > # T2: return without executing any task > # T1: return without executing any task > Failure example: http://ci.infinispan.org/viewLog.html?buildId=27153&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5524) Race condition in SemaphoreCompletionService.executeFront()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5524?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5524: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1229181 > Race condition in SemaphoreCompletionService.executeFront() > ----------------------------------------------------------- > > Key: ISPN-5524 > URL: https://issues.jboss.org/browse/ISPN-5524 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.0.0.Alpha2, 7.2.3.Final > > > If two threads call {{executeFront()}} at the same time, it's possible that none of them executes any task, although there are permits available, and one of the threads just added a task in the queue. This scenario causes random initial state transfer timeouts in the testsuite: > # T1: continueTaskInBackground(): queue = empty, permits = 0 > # T1: backgroundTaskFinished() > # T1: = semaphore.release(): queue = empty, permits = 1 > # T1: = executeFront() > # T1: == semaphore.acquire() -> true: queue = empty, permits = 0 > # T2: == queue.poll() -> null > # T2: submit(task) > # T2: = executeFront() > # T2: == semaphore.acquire() -> false > # T2: return without executing any task > # T1: return without executing any task > Failure example: http://ci.infinispan.org/viewLog.html?buildId=27153&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5524) Race condition in SemaphoreCompletionService.executeFront()

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5524?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5524: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3524, https://github.com/infinispan/infinispan/pull/3525 > Race condition in SemaphoreCompletionService.executeFront() > ----------------------------------------------------------- > > Key: ISPN-5524 > URL: https://issues.jboss.org/browse/ISPN-5524 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.0.0.Alpha2, 7.2.3.Final > > > If two threads call {{executeFront()}} at the same time, it's possible that none of them executes any task, although there are permits available, and one of the threads just added a task in the queue. This scenario causes random initial state transfer timeouts in the testsuite: > # T1: continueTaskInBackground(): queue = empty, permits = 0 > # T1: backgroundTaskFinished() > # T1: = semaphore.release(): queue = empty, permits = 1 > # T1: = executeFront() > # T1: == semaphore.acquire() -> true: queue = empty, permits = 0 > # T2: == queue.poll() -> null > # T2: submit(task) > # T2: = executeFront() > # T2: == semaphore.acquire() -> false > # T2: return without executing any task > # T1: return without executing any task > Failure example: http://ci.infinispan.org/viewLog.html?buildId=27153&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5527) Java system properties no longer supported in leveldb expiration path

by Horia Chiorean (JIRA)

[ https://issues.jboss.org/browse/ISPN-5527?page=com.atlassian.jira.plugin.... ] Horia Chiorean updated ISPN-5527: --------------------------------- Comment: was deleted (was: Since there is nothing the ModeShape codebase can do, we can keep this open for documentation purposes only. ) > Java system properties no longer supported in leveldb expiration path > --------------------------------------------------------------------- > > Key: ISPN-5527 > URL: https://issues.jboss.org/browse/ISPN-5527 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.2.0.Final > Reporter: Paul Richardson > > In 6.0, it was possible to create a leveldb cache configuration like: > {code} > <leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" > location="${user.home}/.komodo/db/data" > expiredLocation="${user.home}/.komodo/db/expired" > implementationType="JAVA"> > </leveldbStore> > {code} > Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute: > {code} > <leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" > path="${user.home}/.komodo/db/data"> > <expiration path="${user.home}/.komodo/db/expired"/> > <implementation type="JAVA"/> > </leveldb-store> > {code} > Looking at the [LevelDBStoreConfigurationParser72|https://github.com/infinispan/infinispa...] class, the method parseLevelDBCacheStore() (line 55) has a call to: > {code} > String value = StringPropertyReplacer.replaceProperties(attributeValue); > {code} > while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5527) Java system properties no longer supported in leveldb expiration path

by Horia Chiorean (JIRA)

[ https://issues.jboss.org/browse/ISPN-5527?page=com.atlassian.jira.plugin.... ] Horia Chiorean commented on ISPN-5527: -------------------------------------- Since there is nothing the ModeShape codebase can do, we can keep this open for documentation purposes only. > Java system properties no longer supported in leveldb expiration path > --------------------------------------------------------------------- > > Key: ISPN-5527 > URL: https://issues.jboss.org/browse/ISPN-5527 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.2.0.Final > Reporter: Paul Richardson > > In 6.0, it was possible to create a leveldb cache configuration like: > {code} > <leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" > location="${user.home}/.komodo/db/data" > expiredLocation="${user.home}/.komodo/db/expired" > implementationType="JAVA"> > </leveldbStore> > {code} > Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute: > {code} > <leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" > path="${user.home}/.komodo/db/data"> > <expiration path="${user.home}/.komodo/db/expired"/> > <implementation type="JAVA"/> > </leveldb-store> > {code} > Looking at the [LevelDBStoreConfigurationParser72|https://github.com/infinispan/infinispa...] class, the method parseLevelDBCacheStore() (line 55) has a call to: > {code} > String value = StringPropertyReplacer.replaceProperties(attributeValue); > {code} > while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3797) DataContainer should interact atomically with Persistence

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3797?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3797: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1229105|https://bugzilla.redhat.com/show_bug.cgi?id=1229105] from NEW to MODIFIED > DataContainer should interact atomically with Persistence > --------------------------------------------------------- > > Key: ISPN-3797 > URL: https://issues.jboss.org/browse/ISPN-3797 > Project: Infinispan > Issue Type: Enhancement > Components: Eviction, Loaders and Stores > Affects Versions: 6.0.0.Final, 5.2.10.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha3, 7.0.0.Final, 5.2.11.Final > > > DataContainer should handle atomically all the interactions with the Persistence. This includes all the eviction/passivation. > Main points: > * In DataContainer load/store will avoid any lose of data during concurrent operations > * Take advantage of CHMv8 > * CacheLoader and Writer Interceptors are no longer needed. > Check the mailling list for more info. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2015