August 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4498) OutOfMemoryError when CI is ran with tracing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4498?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4498: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1131633|https://bugzilla.redhat.com/show_bug.cgi?id=1131633] from NEW to POST > OutOfMemoryError when CI is ran with tracing > -------------------------------------------- > > Key: ISPN-4498 > URL: https://issues.jboss.org/browse/ISPN-4498 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5 > > > The CI will fail very often when tracing is enabled with some sort of OOM error. > http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp... > Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads. > I have created JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4498) OutOfMemoryError when CI is ran with tracing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4498?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4498: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1131633 > OutOfMemoryError when CI is ran with tracing > -------------------------------------------- > > Key: ISPN-4498 > URL: https://issues.jboss.org/browse/ISPN-4498 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5 > > > The CI will fail very often when tracing is enabled with some sort of OOM error. > http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp... > Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads. > I have created JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4559) Replace fails with cache loader

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4559?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4559: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2808 > Replace fails with cache loader > ------------------------------- > > Key: ISPN-4559 > URL: https://issues.jboss.org/browse/ISPN-4559 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores > Affects Versions: 7.0.0.Alpha5 > Reporter: Dennis Reed > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.0.0.Beta2 > > > cache.replace(key, oldValue, newValue) compares the current value in the cache to oldValue, and if they differ it turns into a no-op. > However, CacheLoaderInterceptor does not load entries for a ReplaceCommand. > If the entry only exists in the loader and not in memory, this causes the replace to fail. > CacheLoaderInterceptor must always load the value for a ReplaceCommand. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4649) RemoveCommand does not activate the key in Passivation

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4649?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4649: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2808 > RemoveCommand does not activate the key in Passivation > ------------------------------------------------------ > > Key: ISPN-4649 > URL: https://issues.jboss.org/browse/ISPN-4649 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.0.0.Beta1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Beta2 > > > The RemoveCommand does not activate the key in CacheStore. This creates an inconsistency because the key is never really removed. More precisely, the key is removed from DataContainer but not from CacheStore and during any operation, the old value is loaded from the CacheStore. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4648) Log rebalancing messages to specific category

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4648?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4648: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1131117|https://bugzilla.redhat.com/show_bug.cgi?id=1131117] from ASSIGNED to POST > Log rebalancing messages to specific category > --------------------------------------------- > > Key: ISPN-4648 > URL: https://issues.jboss.org/browse/ISPN-4648 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Beta2, 7.0.0.Final > > > For ease of management, logging of major rebalancing events should be sent to an appropriate category. > Use org.infinispan.CLUSTER and level INFO -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4498) OutOfMemoryError when CI is ran with tracing

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4498?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4498: -------------------------------- Description: The CI will fail very often when tracing is enabled with some sort of OOM error. http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp... Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads. I have created JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC. was: The CI will fail very often when tracing is enabled with some sort of OOM error. http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp... Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads. I have crated JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC. > OutOfMemoryError when CI is ran with tracing > -------------------------------------------- > > Key: ISPN-4498 > URL: https://issues.jboss.org/browse/ISPN-4498 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5 > > > The CI will fail very often when tracing is enabled with some sort of OOM error. > http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp... > Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads. > I have created JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4569) Inserting into cache with indexing fails for XA transactions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4569: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1130493|https://bugzilla.redhat.com/show_bug.cgi?id=1130493] from NEW to POST > Inserting into cache with indexing fails for XA transactions > ------------------------------------------------------------ > > Key: ISPN-4569 > URL: https://issues.jboss.org/browse/ISPN-4569 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Embedded Querying, Transactions > Affects Versions: 7.0.0.Alpha5 > Reporter: Radim Vansa > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > If I setup XA transactions in {{ClusteredQueryDslConditionsTest}} using > {code} > cacheCfg.transaction().transactionMode(TransactionMode.TRANSACTIONAL).useSynchronization(false); > {code} > the test fails. The reason is in deadlock while updating {{ScopedKey}} in __cluster_registry_cache__ : It seems that on originator we create transaction with modified inserted key and the {{ScopedKey}} for inserted class, and send it in two prepare commands to the other node. In the {{ScopedKey}}-prepare, the lock is acquired, but the regular prepare on the other node does not see it (it is not committed yet) and also tries to update this {{ScopedKey}} in __cluster_registry_cache__ . This fails with lock timeout, as the commit is waiting on the regular prepare to finish. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4520) JdbcBinaryStoreTest.testLoadAndStoreWithLifespanAndIdle random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4520?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-4520. -------------------------------- Resolution: Done Ok, re-closing this one. > JdbcBinaryStoreTest.testLoadAndStoreWithLifespanAndIdle random failures > ----------------------------------------------------------------------- > > Key: ISPN-4520 > URL: https://issues.jboss.org/browse/ISPN-4520 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core, Test Suite - Core > Affects Versions: 7.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.Beta1, 7.0.0.Alpha5 > > > I think the 1s timeout is a bit small for the CI machine: > {noformat} > java.lang.IllegalStateException: Purge has timed out > at org.infinispan.persistence.BaseStoreTest.purgeExpired(BaseStoreTest.java:268) > {noformat} > The other methods using {{BaseStoreTest.purgeExpired}} and the other tests extending BaseStoreTest probably have the same problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4652) Passivation with shared CacheLoader is not working properly

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-4652: --------------------------------- Summary: Passivation with shared CacheLoader is not working properly Key: ISPN-4652 URL: https://issues.jboss.org/browse/ISPN-4652 Project: Infinispan Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 7.0.0.Beta2 The activation does not interact with the shared cache store. This creates a problem for the RemoveCommand (at least) since the value is never removed (similar to https://issues.jboss.org/browse/ISPN-4649) Unfortunately, this will need a little more thinking how to solve it since only the primary owner should activate (i.e. remove it) from the shared store. Tests in LocalConditionalCommandTest and ClusteredConditionalCommandTest are disabled to because they are hitting this issue. (ps to myself: don't forget to re-enabled them) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4520) JdbcBinaryStoreTest.testLoadAndStoreWithLifespanAndIdle random failures

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4520?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-4520: ----------------------------------- [~dan.berindei] not related to this particular issue, but I have already a JIRA for the JpaStore: https://issues.jboss.org/browse/ISPN-4582 > JdbcBinaryStoreTest.testLoadAndStoreWithLifespanAndIdle random failures > ----------------------------------------------------------------------- > > Key: ISPN-4520 > URL: https://issues.jboss.org/browse/ISPN-4520 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core, Test Suite - Core > Affects Versions: 7.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.Alpha5, 7.0.0.Beta1 > > > I think the 1s timeout is a bit small for the CI machine: > {noformat} > java.lang.IllegalStateException: Purge has timed out > at org.infinispan.persistence.BaseStoreTest.purgeExpired(BaseStoreTest.java:268) > {noformat} > The other methods using {{BaseStoreTest.purgeExpired}} and the other tests extending BaseStoreTest probably have the same problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 2014