August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5664) Null is returned for a not expired entry in Hot Rod client

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5664?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5664: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1243671|https://bugzilla.redhat.com/show_bug.cgi?id=1243671] from ASSIGNED to POST > Null is returned for a not expired entry in Hot Rod client > ---------------------------------------------------------- > > Key: ISPN-5664 > URL: https://issues.jboss.org/browse/ISPN-5664 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > For a mortal entry (lifespan > -1), overwriting it with lifespan=-1 (make it immortal) unexpectedly removes the entry like follows. > ~~~ > cache.put(key, "value1", 100, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value1" > cache.put(key, "value2", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns null, expected "value2" > cache.put(key, "value3", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value3" > ~~~ > In library mode, the 2nd get returns non-null as expected. The same behaviour is observed for a transient (maxIdle > -1) entry also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5673) Observation attribute is ignored for listeners with indexed DSL filters

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5673?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5673: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3643, https://github.com/infinispan/infinispan/pull/3644 (was: https://github.com/infinispan/infinispan/pull/3643) > Observation attribute is ignored for listeners with indexed DSL filters > ----------------------------------------------------------------------- > > Key: ISPN-5673 > URL: https://issues.jboss.org/browse/ISPN-5673 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.CR1, 8.0.0.Final, 7.2.5.Final > > > Both pre and post events are fired even if observation was set to POST only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5669) JPAProtobufFilterIndexingServiceProvider is ignored

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5669?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5669: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3643, https://github.com/infinispan/infinispan/pull/3644 (was: https://github.com/infinispan/infinispan/pull/3643) > JPAProtobufFilterIndexingServiceProvider is ignored > --------------------------------------------------- > > Key: ISPN-5669 > URL: https://issues.jboss.org/browse/ISPN-5669 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Beta3 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.CR1, 8.0.0.Final, 7.2.5.Final > > > The processor of the @MetaInfServices annotation detects the class JPAFilterIndexingServiceProvider as the implemented contract instead of the intended FilterIndexingServiceProvider interface. This can be easily overridden manually. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4599) InfinispanIndexManager locks held when primary node change

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4599?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4599: ----------------------------------------------- yu zheng <yuzheng(a)redhat.com> changed the Status of [bug 1|https://bugzilla.stage.redhat.com/show_bug.cgi?id=1] from CLOSED to ON_QA > InfinispanIndexManager locks held when primary node change > ---------------------------------------------------------- > > Key: ISPN-4599 > URL: https://issues.jboss.org/browse/ISPN-4599 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 7.0.0.Alpha5 > Reporter: Gustavo Fernandes > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 7.0.0.Beta2 > > > Given the following configuration: > {code:xml} > <cache-container name="store" default-cache="default" statistics="true"> > <transport cluster="Infinispan-Query-Cluster"/> >  >  >  > <replicated-cache name="passivation" mode="SYNC" remote-timeout="20000" statistics="true"> > <indexing index="LOCAL"> > <property name="hibernate.search.default.indexmanager"> > org.infinispan.query.indexmanager.InfinispanIndexManager > </property> > <property name="hibernate.search.default.directory_provider">infinispan</property> > </indexing> > </replicated-cache> > <replicated-cache name="LuceneIndexesMetadata" mode="SYNC" remote-timeout="25000"> > <indexing index="NONE"/> > </replicated-cache> > <distributed-cache name="LuceneIndexesData" mode="SYNC" remote-timeout="25000"> > <indexing index="NONE"/> > </distributed-cache> > <replicated-cache name="LuceneIndexesLocking" mode="SYNC" remote-timeout="25000"> > <indexing index="NONE"/> > </replicated-cache> > </cache-container> > {code} > Scenario: > - Start Node 1 > - Insert a few @Indexed objects in the cache > - Start Node 2 > - Insert a few @Indexed objects in the cache > Node 2 cannot acquire the locks to write and throws errors: > {code} > org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask applyUpdates > ERROR: HSEARCH000072: Couldn't open the IndexWriter because of previous error: operation skipped, index ouf of sync! > Aug 01, 2014 4:48:23 PM org.hibernate.search.exception.impl.LogErrorHandler handleException > ERROR: HSEARCH000058: Exception occurred org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: org.infinispan.lucene.locking.BaseLuceneLock@2c1e889f > {code} > During the insertion on Node1, the InfinispanCommandsBackend elects Node 1 as the primary node (since it's the only one) and acquires the lock on the LuceneIndexesLocking. > When node 2 joins and the topology changes, the InfinispanCommandsBackend elects Node 2 as the primary node, but it fails to acquire the lock (held by Node 1) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5679) Add clustered expiration support

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5679?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5679: -------------------------------- Status: Open (was: New) > Add clustered expiration support > -------------------------------- > > Key: ISPN-5679 > URL: https://issues.jboss.org/browse/ISPN-5679 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 8.0.0.Final > > > ISPN-694 added support for in memory expiration which is synchronized with the cache store. However we also need across clustered expiration synchronization. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5679) Add clustered expiration support

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5679?page=com.atlassian.jira.plugin.... ] Work on ISPN-5679 started by William Burns. ------------------------------------------- > Add clustered expiration support > -------------------------------- > > Key: ISPN-5679 > URL: https://issues.jboss.org/browse/ISPN-5679 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 8.0.0.Final > > > ISPN-694 added support for in memory expiration which is synchronized with the cache store. However we also need across clustered expiration synchronization. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5679) Add clustered expiration support

by William Burns (JIRA)

William Burns created ISPN-5679: ----------------------------------- Summary: Add clustered expiration support Key: ISPN-5679 URL: https://issues.jboss.org/browse/ISPN-5679 Project: Infinispan Issue Type: Sub-task Components: Core Reporter: William Burns Assignee: William Burns Fix For: 8.0.0.CR1, 8.0.0.Final ISPN-694 added support for in memory expiration which is synchronized with the cache store. However we also need across clustered expiration synchronization. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3064) Extend cache expiration notification to cache stores

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3064?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-3064. --------------------------------- Fix Version/s: 8.0.0.CR1 8.0.0.Final Resolution: Duplicate Issue This was resolved in ISPN-694 > Extend cache expiration notification to cache stores > ---------------------------------------------------- > > Key: ISPN-3064 > URL: https://issues.jboss.org/browse/ISPN-3064 > Project: Infinispan > Issue Type: Feature Request > Components: Listeners, Loaders and Stores > Reporter: Galder Zamarreño > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Extend cache entry expiration notifications to situations where CacheStore instances, via purgeExpired(), expire data directly in the cache store. This is an extension of ISPN-694. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3960) Eviction notification from entry expired in cache store

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3960?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-3960. --------------------------------- Fix Version/s: 8.0.0.CR1 8.0.0.Final Resolution: Duplicate Issue This was fixed in ISPN-694 > Eviction notification from entry expired in cache store > ------------------------------------------------------- > > Key: ISPN-3960 > URL: https://issues.jboss.org/browse/ISPN-3960 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.1.Final > Reporter: Radim Vansa > Labels: 630 > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Looking on PersistenceManagerImpl, it seems to me that if cache store expires an entry, CacheEntryEvicted event is fired. > There is no expiration event currently, but that's no excuse for firing the wrong event. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-694) Create expiration notification for in-memory cache entries

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-694?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-694: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.0.0.CR1 Resolution: Done > Create expiration notification for in-memory cache entries > ---------------------------------------------------------- > > Key: ISPN-694 > URL: https://issues.jboss.org/browse/ISPN-694 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Environment: any > Reporter: Edouard Boily > Assignee: William Burns > Fix For: 8.0.0.CR1, 8.0.0.Final > > Attachments: 01.patch > > > Create a CacheEntryExpired notification and make EvictionManager send this notification when a cache entry is evicted because it is expired. > Also mage sure the cache entry value is sent over in the event. > CacheEntryEvicted notification should also send the entry value in the event. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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