September 2014 - infinispan-issues

[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: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1139642|https://bugzilla.redhat.com/show_bug.cgi?id=1139642] from NEW to MODIFIED > OutOfMemoryError when CI is ran with tracing > -------------------------------------------- > > Key: ISPN-4498 > URL: https://issues.jboss.org/browse/ISPN-4498 > Project: Infinispan > Issue Type: Bug > 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.3.1#6329)

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 References: https://bugzilla.redhat.com/show_bug.cgi?id=1131633, https://bugzilla.redhat.com/show_bug.cgi?id=1139642 (was: 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 > 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.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4409) LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4409?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4409: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1108089|https://bugzilla.redhat.com/show_bug.cgi?id=1108089] from ON_QA to VERIFIED > LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError > ---------------------------------------------------------------------------------------- > > Key: ISPN-4409 > URL: https://issues.jboss.org/browse/ISPN-4409 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha5 > > > The LevelDBCacheStoreIT fails to start with an error resulting from initialising the server side cache marshaller. The way the cache manager is created is not correct. You might as well just use the same marshaller as for the client. > Even if you really need a cache's marshaller, you should get it via an injected cache rather than initialising a cache from scratch. > {code}com.arjuna.ats.arjuna.exceptions.FatalError: null > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:96) > at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:300) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1146) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.getTransaction(TransactionManagerImple.java:69) > at org.infinispan.cache.impl.CacheImpl.getOngoingTransaction(CacheImpl.java:1414) > at org.infinispan.cache.impl.CacheImpl.getInvocationContextForRead(CacheImpl.java:592) > at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:474) > at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:469) > at org.infinispan.registry.impl.ClusterRegistryImpl.keys(ClusterRegistryImpl.java:81) > at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:67) > at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132) > at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114) > at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:381) > at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.getServerMarshaller(LevelDBCacheStoreIT.java:190) > at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.<clinit>(LevelDBCacheStoreIT.java:67) > « Hide stacktrace{code} > The fix gets past this particular error but it still shows this afterwards: > {code}Caused by: javax.management.InstanceNotFoundException: jboss.infinispan:type=Server,name=HotRod,component=Transport{code} > Tristan is working on this... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4409) LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4409?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4409: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1139633|https://bugzilla.redhat.com/show_bug.cgi?id=1139633] from NEW to MODIFIED > LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError > ---------------------------------------------------------------------------------------- > > Key: ISPN-4409 > URL: https://issues.jboss.org/browse/ISPN-4409 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha5 > > > The LevelDBCacheStoreIT fails to start with an error resulting from initialising the server side cache marshaller. The way the cache manager is created is not correct. You might as well just use the same marshaller as for the client. > Even if you really need a cache's marshaller, you should get it via an injected cache rather than initialising a cache from scratch. > {code}com.arjuna.ats.arjuna.exceptions.FatalError: null > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:96) > at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:300) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1146) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.getTransaction(TransactionManagerImple.java:69) > at org.infinispan.cache.impl.CacheImpl.getOngoingTransaction(CacheImpl.java:1414) > at org.infinispan.cache.impl.CacheImpl.getInvocationContextForRead(CacheImpl.java:592) > at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:474) > at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:469) > at org.infinispan.registry.impl.ClusterRegistryImpl.keys(ClusterRegistryImpl.java:81) > at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:67) > at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132) > at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114) > at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:381) > at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.getServerMarshaller(LevelDBCacheStoreIT.java:190) > at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.<clinit>(LevelDBCacheStoreIT.java:67) > « Hide stacktrace{code} > The fix gets past this particular error but it still shows this afterwards: > {code}Caused by: javax.management.InstanceNotFoundException: jboss.infinispan:type=Server,name=HotRod,component=Transport{code} > Tristan is working on this... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4409) LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4409?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4409: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1108089, https://bugzilla.redhat.com/show_bug.cgi?id=1139633 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1108089) > LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError > ---------------------------------------------------------------------------------------- > > Key: ISPN-4409 > URL: https://issues.jboss.org/browse/ISPN-4409 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha5 > > > The LevelDBCacheStoreIT fails to start with an error resulting from initialising the server side cache marshaller. The way the cache manager is created is not correct. You might as well just use the same marshaller as for the client. > Even if you really need a cache's marshaller, you should get it via an injected cache rather than initialising a cache from scratch. > {code}com.arjuna.ats.arjuna.exceptions.FatalError: null > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:96) > at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:300) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1146) > at com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.getTransaction(TransactionManagerImple.java:69) > at org.infinispan.cache.impl.CacheImpl.getOngoingTransaction(CacheImpl.java:1414) > at org.infinispan.cache.impl.CacheImpl.getInvocationContextForRead(CacheImpl.java:592) > at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:474) > at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:469) > at org.infinispan.registry.impl.ClusterRegistryImpl.keys(ClusterRegistryImpl.java:81) > at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:67) > at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132) > at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114) > at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:381) > at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.getServerMarshaller(LevelDBCacheStoreIT.java:190) > at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.<clinit>(LevelDBCacheStoreIT.java:67) > « Hide stacktrace{code} > The fix gets past this particular error but it still shows this afterwards: > {code}Caused by: javax.management.InstanceNotFoundException: jboss.infinispan:type=Server,name=HotRod,component=Transport{code} > Tristan is working on this... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4640) Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4640?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4640: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1130648|https://bugzilla.redhat.com/show_bug.cgi?id=1130648] from ON_QA to VERIFIED > Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-4640 > URL: https://issues.jboss.org/browse/ISPN-4640 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.0.0.Beta2 > > > This enhancement is needed for performance and should make FilterAndConverter class obsolete. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4640) Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4640?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4640: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1139631|https://bugzilla.redhat.com/show_bug.cgi?id=1139631] from NEW to MODIFIED > Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-4640 > URL: https://issues.jboss.org/browse/ISPN-4640 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.0.0.Beta2 > > > This enhancement is needed for performance and should make FilterAndConverter class obsolete. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4640) Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4640?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4640: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1130648, https://bugzilla.redhat.com/show_bug.cgi?id=1139631 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1130648) > Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-4640 > URL: https://issues.jboss.org/browse/ISPN-4640 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.0.0.Beta2 > > > This enhancement is needed for performance and should make FilterAndConverter class obsolete. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4602) Verify EntryIterator works with MarshalledValues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4602?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4602: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1128811|https://bugzilla.redhat.com/show_bug.cgi?id=1128811] from ON_QA to VERIFIED > Verify EntryIterator works with MarshalledValues > ------------------------------------------------ > > Key: ISPN-4602 > URL: https://issues.jboss.org/browse/ISPN-4602 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 7.0.0.Alpha5 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Beta1 > > > The EntryIterator currently doesn't deserialize MarshalledValues as needed which would cause filter failures and the incorrect values to be returned. > This also means each key/value pair would need to be deserialized when applied to filter which will be slower and should be noted in documentation, but sent across as MarshalledValues?. The only other way is to use some sort of proxy for each object to force lazy deserialization on referencing a field when applying filter, but this seems overkill. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4602) Verify EntryIterator works with MarshalledValues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4602?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4602: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1139629|https://bugzilla.redhat.com/show_bug.cgi?id=1139629] from NEW to MODIFIED > Verify EntryIterator works with MarshalledValues > ------------------------------------------------ > > Key: ISPN-4602 > URL: https://issues.jboss.org/browse/ISPN-4602 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 7.0.0.Alpha5 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Beta1 > > > The EntryIterator currently doesn't deserialize MarshalledValues as needed which would cause filter failures and the incorrect values to be returned. > This also means each key/value pair would need to be deserialized when applied to filter which will be slower and should be noted in documentation, but sent across as MarshalledValues?. The only other way is to use some sort of proxy for each object to force lazy deserialization on referencing a field when applying filter, but this seems overkill. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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