June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4411) Server testsuite must use the new management port (9990) instead of the old one(9999)

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4411: ------------------------------------- Summary: Server testsuite must use the new management port (9990) instead of the old one(9999) Key: ISPN-4411 URL: https://issues.jboss.org/browse/ISPN-4411 Project: Infinispan Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tristan Tarrant Assignee: Mircea Markus -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4411) Server testsuite must use the new management port (9990) instead of the old one(9999)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4411?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4411: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Server testsuite must use the new management port (9990) instead of the old one(9999) > ------------------------------------------------------------------------------------- > > Key: ISPN-4411 > URL: https://issues.jboss.org/browse/ISPN-4411 > Project: Infinispan > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4410) Remove superfluous elements/attributes from server configurations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4410?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4410: ---------------------------------- Description: The locking isolation attribute is now being ignored since ISPN-4302 The jgroups configuration no longer needs Discovery.timeout and Discover.initial_num_hosts The server no longer has a management-native port was:The locking isolation attribute is now being ignored since ISPN-4302 > Remove superfluous elements/attributes from server configurations > ----------------------------------------------------------------- > > Key: ISPN-4410 > URL: https://issues.jboss.org/browse/ISPN-4410 > Project: Infinispan > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The locking isolation attribute is now being ignored since ISPN-4302 > The jgroups configuration no longer needs Discovery.timeout and Discover.initial_num_hosts > The server no longer has a management-native port -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4410) Remove superfluous elements/attributes from server configurations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4410?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4410: ---------------------------------- Summary: Remove superfluous elements/attributes from server configurations (was: Remove superfluous isolation attribute from server configurations) > Remove superfluous elements/attributes from server configurations > ----------------------------------------------------------------- > > Key: ISPN-4410 > URL: https://issues.jboss.org/browse/ISPN-4410 > Project: Infinispan > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The locking isolation attribute is now being ignored since ISPN-4302 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4410) Remove superfluous isolation attribute from server configurations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4410?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4410: ---------------------------------- Summary: Remove superfluous isolation attribute from server configurations (was: Rmove superfluous isolation attribute from server configurations) > Remove superfluous isolation attribute from server configurations > ----------------------------------------------------------------- > > Key: ISPN-4410 > URL: https://issues.jboss.org/browse/ISPN-4410 > Project: Infinispan > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tristan Tarrant > Assignee: Mircea Markus > > The locking isolation attribute is now being ignored since ISPN-4302 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4410) Remove superfluous isolation attribute from server configurations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4410?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4410: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Remove superfluous isolation attribute from server configurations > ----------------------------------------------------------------- > > Key: ISPN-4410 > URL: https://issues.jboss.org/browse/ISPN-4410 > Project: Infinispan > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The locking isolation attribute is now being ignored since ISPN-4302 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3421) Transaction is sometimes not applied on all owners if originator dies during commit

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3421?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3421: ------------------------------- Summary: Transaction is sometimes not applied on all owners if originator dies during commit (was: State Transfer can leave keys on < numOwners nodes for transactional caches.) > Transaction is sometimes not applied on all owners if originator dies during commit > ----------------------------------------------------------------------------------- > > Key: ISPN-3421 > URL: https://issues.jboss.org/browse/ISPN-3421 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: State Transfer > Affects Versions: 5.2.7.Final > Reporter: Erik Salter > Assignee: Dan Berindei > Priority: Critical > > There's a hole in state transfer mechanism that can occur when a node is leaving the cluster, but it was creating the entries and was only able to replicate the data to some of the nodes. > The problem occurs when the segment ownership of the node doesn't change after the rebalance. Since state transfer does not request state for keys in which it is already an owner, the cache could be left in a state where a key is resident < numOwners nodes. In addition, this could be any subset of the primary OR backup nodes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4410) Rmove superfluous isolation attribute from server configurations

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4410: ------------------------------------- Summary: Rmove superfluous isolation attribute from server configurations Key: ISPN-4410 URL: https://issues.jboss.org/browse/ISPN-4410 Project: Infinispan Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tristan Tarrant Assignee: Mircea Markus The locking isolation attribute is now being ignored since ISPN-4302 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-4409: -------------------------------------- Summary: 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 Security Level: Public (Everyone can see) 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.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4272) Refactoring of ISPN Server Testsuite

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4272?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-4272: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/2552, https://github.com/infinispan/infinispan/pull/2645 (was: https://github.com/infinispan/infinispan/pull/2552) > Refactoring of ISPN Server Testsuite > ------------------------------------ > > Key: ISPN-4272 > URL: https://issues.jboss.org/browse/ISPN-4272 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Reporter: Vitalii Chepeliuk > Assignee: Vitalii Chepeliuk > Priority: Minor > Fix For: 7.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 June 2014