August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5559) "AsyncCacheWriter is dead!" errors cause deadlock or unbounded use of memory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5559?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5559: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1235140|https://bugzilla.redhat.com/show_bug.cgi?id=1235140] from MODIFIED to ON_QA > "AsyncCacheWriter is dead!" errors cause deadlock or unbounded use of memory > ---------------------------------------------------------------------------- > > Key: ISPN-5559 > URL: https://issues.jboss.org/browse/ISPN-5559 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 5.3.0.Final, 6.0.0.Final, 7.0.0.Final > Reporter: Karsten Blees > Fix For: 8.0.0.Beta1, 7.2.4.Final > > > Caused by a relatively small AsyncStore shutdownTimeout (default 25s) in conjunction with large queue sizes or slow back-end stores. > With assertions enabled, the coordinator thread will exit with AssertionError and the AsyncStore will deadlock, as no more changes are beeing processed. > With assertions disabled, the coordinator thread will allocate an unbounded number of AsyncStoreProcessors. If AsyncStoreProcessors were multithreaded (see ISPN-3532), this would cause loss of data (due to older changes overwriting newer changes in the back-end store). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5379) Persistence with stringKeyedJdbcStore throwing ConcurrentModificationException while adding data to cache

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5379?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5379: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1212505|https://bugzilla.redhat.com/show_bug.cgi?id=1212505] from MODIFIED to ON_QA > Persistence with stringKeyedJdbcStore throwing ConcurrentModificationException while adding data to cache > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-5379 > URL: https://issues.jboss.org/browse/ISPN-5379 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.0.0.Beta3 > > > From Dennis Reed: > A ConcurrentModificationException in the CacheWriter interceptor during a commit. > java.util.ConcurrentModificationException > at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:953) > at java.util.LinkedList$ListItr.next(LinkedList.java:886) > at org.infinispan.interceptors.CacheWriterInterceptor.store(CacheWriterInterceptor.java:210) > at org.infinispan.interceptors.CacheWriterInterceptor.commitCommand(CacheWriterInterceptor.java:115) > The code is looping through the modifications associated with the transaction: > List<WriteCommand> modifications = ctx.getCacheTransaction().getAllModifications(); > ... > 210: for (WriteCommand cacheCommand : modifications) { > The transaction's modification list is stored as a synchronized list with a comment "we need to synchronize this collection to be able to get a valid snapshot from another thread during state transfer". > But this thread is not doing state transfer, and I'd assume "get a valid snapshot" wouldn't include modification? > Is it valid for this list to be modified from another thread (in which case all iterations should be synchronized), or is something modifying it incorrectly? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5562) AsyncCacheWriter should write all data to the back-end store before shutting down

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5562?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5562: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1235143|https://bugzilla.redhat.com/show_bug.cgi?id=1235143] from MODIFIED to ON_QA > AsyncCacheWriter should write all data to the back-end store before shutting down > --------------------------------------------------------------------------------- > > Key: ISPN-5562 > URL: https://issues.jboss.org/browse/ISPN-5562 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.0.Final, 6.0.0.Final, 7.0.0.Final > Reporter: Karsten Blees > Fix For: 8.0.0.Beta1, 7.2.4.Final > > > There is a chance that AsyncCacheWriter may stop before writing all midifications to the back-end store. This can primarily happen when writing the same keys in rapid succession. The coordinator thread will move these modifications to the head state (because of conflicts with tail), which is not checked before shutdown. > There are two other minor race conditions if stop() is called concurrently to write() or clear() - these cannot happen in practice because PassivationManager is stopped before PersistenceManager: > 1. AsyncStoreCoordinator checks State.stopped and State.modifications.isEmpty() without holding the readLock(). This is not reliable because a concurrent write() or remove() may still add to the modifications map. > 2. clear() just replaces the head state, without copying the stopped flag that may have been set by a concurrent stop(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5595) Operation [Registering Deployed Cache Store service...] happens too late on slower machines

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5595?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5595: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1223395|https://bugzilla.redhat.com/show_bug.cgi?id=1223395] from MODIFIED to ON_QA > Operation [Registering Deployed Cache Store service...] happens too late on slower machines > ------------------------------------------------------------------------------------------- > > Key: ISPN-5595 > URL: https://issues.jboss.org/browse/ISPN-5595 > Project: Infinispan > Issue Type: Bug > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5564) AsyncCacheWriter stop() and clear() should not wait for space in the modifications queue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5564?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5564: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1235165|https://bugzilla.redhat.com/show_bug.cgi?id=1235165] from MODIFIED to ON_QA > AsyncCacheWriter stop() and clear() should not wait for space in the modifications queue > ---------------------------------------------------------------------------------------- > > Key: ISPN-5564 > URL: https://issues.jboss.org/browse/ISPN-5564 > Project: Infinispan > Issue Type: Enhancement > Reporter: Karsten Blees > Fix For: 8.0.0.Beta1, 7.2.4.Final > > > AsyncCacheWriter.clear() invalidates all enqueued changes rather than adding more changes to the queue. Thus, clear should not wait if the queue is full. > AsyncCacheWriter.stop() should also take effect immediately (i.e. set the stopped flag *without* waiting if the queue is full). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4914) The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file'

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4914?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4914: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1229875|https://bugzilla.redhat.com/show_bug.cgi?id=1229875] from MODIFIED to ON_QA > The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file' > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-4914 > URL: https://issues.jboss.org/browse/ISPN-4914 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.0.0.Final > > > The server only supports READ_COMMITTED isolation and should print a warning in case someone sets a value. Unfortunately the check is wrong and the warning is always printed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5607) NearCache: it is possible to read stale data with a put/remove followed by a get

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5607?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5607: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1244133|https://bugzilla.redhat.com/show_bug.cgi?id=1244133] from MODIFIED to ON_QA > NearCache: it is possible to read stale data with a put/remove followed by a get > -------------------------------------------------------------------------------- > > Key: ISPN-5607 > URL: https://issues.jboss.org/browse/ISPN-5607 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.3.Final > Environment: one hotrod client with 2 hotrod servers > Reporter: Enrico Olivelli > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 8.0.0.Final, 7.2.5.Final > > > Writes to the NearCache do not invalidate/update local data on put/remove operations, and so the NearCache (LAZY MODE) is invalidated using an eventlistener in an asynch way. > It is possible for a client to write a value and issue a get on the same key, and the result of the get would not be the latest value but the one which was present before the update operation. > This happens frequently when there is very much traffic on the connection of the listener which receives the events for the NearCache. > It would be better at least to invalidate locally every entry modified from the client itself -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3532) AsyncStore has only one live AsyncStoreProcessor (thread) in one time

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3532?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3532: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1235146|https://bugzilla.redhat.com/show_bug.cgi?id=1235146] from MODIFIED to ON_QA > AsyncStore has only one live AsyncStoreProcessor (thread) in one time > --------------------------------------------------------------------- > > Key: ISPN-3532 > URL: https://issues.jboss.org/browse/ISPN-3532 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.3.0.Final, 6.0.0.Beta1 > Reporter: Laszlo Hadadi > Fix For: 8.0.0.Beta1, 7.2.4.Final > > > AsyncStore cache modifications processed asynchronously only on one thread in one time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5563) AsyncCacheLoader.load() may still return stale data

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5563?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5563: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1235134|https://bugzilla.redhat.com/show_bug.cgi?id=1235134] from MODIFIED to ON_QA > AsyncCacheLoader.load() may still return stale data > --------------------------------------------------- > > Key: ISPN-5563 > URL: https://issues.jboss.org/browse/ISPN-5563 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.0.0.FINAL, 6.0.0.Final, 7.0.0.Final > Reporter: Karsten Blees > Fix For: 8.0.0.Beta1, 7.2.4.Final > > > There's a race condition that allows AsyncCacheLoader.load() / State.get() to return stale data. If the coordinator thread moves a modification to the head state because of a key conflict with tail, State.get() may miss that modification and return data from the back-end store instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5607) NearCache: it is possible to read stale data with a put/remove followed by a get

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5607?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5607: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1244133|https://bugzilla.redhat.com/show_bug.cgi?id=1244133] from POST to MODIFIED > NearCache: it is possible to read stale data with a put/remove followed by a get > -------------------------------------------------------------------------------- > > Key: ISPN-5607 > URL: https://issues.jboss.org/browse/ISPN-5607 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.3.Final > Environment: one hotrod client with 2 hotrod servers > Reporter: Enrico Olivelli > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 8.0.0.Final, 7.2.5.Final > > > Writes to the NearCache do not invalidate/update local data on put/remove operations, and so the NearCache (LAZY MODE) is invalidated using an eventlistener in an asynch way. > It is possible for a client to write a value and issue a get on the same key, and the result of the get would not be the latest value but the one which was present before the update operation. > This happens frequently when there is very much traffic on the connection of the listener which receives the events for the NearCache. > It would be better at least to invalidate locally every entry modified from the client itself -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 August 2015