December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2579) StateResponseCommand received after the node is removed from CH causes IllegalArgumentException

by Radim Vansa (JIRA)

Radim Vansa created ISPN-2579: --------------------------------- Summary: StateResponseCommand received after the node is removed from CH causes IllegalArgumentException Key: ISPN-2579 URL: https://issues.jboss.org/browse/ISPN-2579 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.0.Beta5 Reporter: Radim Vansa Assignee: Mircea Markus Priority: Minor When a node requests ST and then it receives a CH where this node is not a member, it sends ST request CANCEL_STATE_TRANSFER - however, if the StateResponseCommand is already on its way and reaches the node, it causes {code} java.lang.IllegalArgumentException: Node hyperion947-55285 is not a member at org.infinispan.distribution.ch.DefaultConsistentHash.getSegmentsForOwner(DefaultConsistentHash.java:102) at org.infinispan.statetransfer.StateConsumerImpl.applyState(StateConsumerImpl.java:272) at org.infinispan.statetransfer.StateResponseCommand.perform(StateResponseCommand.java:86) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
5
0 / 0

[JBoss JIRA] (ISPN-2257) SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode still randomly failing

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2257: -------------------------------------- Summary: SimpleCacheRecoveryAdminTest.testForceCommitOnOtherNode still randomly failing Key: ISPN-2257 URL: https://issues.jboss.org/browse/ISPN-2257 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.2.0.Alpha4 The issue is failing again in master: {code}Failed tests: testForceCommitOnOtherNode(org.infinispan.tx.recovery.admin.SimpleCacheRecoveryAdminTest): expected:<false> but was:<true>{code} Unfortunately I don't have any logs. No idea if this is related to NBST at all :( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
6
0 / 0

[JBoss JIRA] (ISPN-2587) Optimize command forwarding after topology changes

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2587: ---------------------------------- Summary: Optimize command forwarding after topology changes Key: ISPN-2587 URL: https://issues.jboss.org/browse/ISPN-2587 Project: Infinispan Issue Type: Task Components: State transfer Affects Versions: 5.2.0.Beta5 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.Final When a node receives a command with a topology id lower than its own topology id, it forwards the command to all the owners in the current topology. This is especially bad in replicated caches, where all the nodes check whether to forward or not, and after a join we may get {{n * (n-1)}} forwarded commands instead of just {{n}}. Most of the time the difference between the current topology id and the command's topology id is <= 1, so we could avoid a lot of the extra forwarding if we kept the previous cache topology and we forwarded the command only to the owners added in the latest topology. Obviously, if the command is older we'd still forward it to all the owners. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2586) Asynchronous FileCacheStore uses a JBossMarshaller with a null ExternalizerTable

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2586: ------------------------------------- Summary: Asynchronous FileCacheStore uses a JBossMarshaller with a null ExternalizerTable Key: ISPN-2586 URL: https://issues.jboss.org/browse/ISPN-2586 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant Assignee: Galder Zamarreño -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] (ISPN-2585) BackupReceiver survives cache shutdown

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2585: ------------------------------------- Summary: BackupReceiver survives cache shutdown Key: ISPN-2585 URL: https://issues.jboss.org/browse/ISPN-2585 Project: Infinispan Issue Type: Enhancement Components: Cross-Site Replication Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Mircea Markus -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
3
0 / 0

[JBoss JIRA] (ISPN-2583) Remove ConfigDoclet and xsom dependency

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2583: ------------------------------------- Summary: Remove ConfigDoclet and xsom dependency Key: ISPN-2583 URL: https://issues.jboss.org/browse/ISPN-2583 Project: Infinispan Issue Type: Enhancement Components: Build process Affects Versions: 5.2.0.Beta5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.Beta6 Remove ConfigDoclet and xsom dependency since we don't need to generate the configuration schema and docs from JAXB annotations anymore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (ISPN-2584) BackupReceiver survives cache shutdown

by Radim Vansa (JIRA)

Radim Vansa created ISPN-2584: --------------------------------- Summary: BackupReceiver survives cache shutdown Key: ISPN-2584 URL: https://issues.jboss.org/browse/ISPN-2584 Project: Infinispan Issue Type: Bug Components: Cross-Site Replication Affects Versions: 5.2.0.Beta5 Reporter: Radim Vansa Assignee: Mircea Markus When the cache manager is stopped together with all caches, the static field {{BackupReceiverRepositoryImpl.backupReceivers}} is not cleaned up. When another cache manager is started and we try to XS replicate into this node, the request reaches {{BackupReceiver}} with references to the old, stopped cache. This instance has TERMINATED ComponentRepository without {{TransactionTable}} and this results in {{NullPointerException}} in {{BackupCacheUpdater.replayModificationsInTransaction}}. When the cache is stopped, it should remove all references to it from the {{BackupReceiverRepositoryImpl.backupReceivers}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2541) MarshallExternalPojosTest.testReplicateJBossExternalizePojoToNewJoiningNode fails randomly

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2541: -------------------------------------- Summary: MarshallExternalPojosTest.testReplicateJBossExternalizePojoToNewJoiningNode fails randomly Key: ISPN-2541 URL: https://issues.jboss.org/browse/ISPN-2541 Project: Infinispan Issue Type: Bug Components: Marshalling Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.CR1 {code}Failed tests: testReplicateJBossExternalizePojoToNewJoiningNode(org.infinispan.marshall.MarshallExternalPojosTest): Replication timeout for MarshallExternalPojosTest-NodeC-10724{code} TRACE log: https://dl.dropbox.com/u/6148072/testReplicateJBossExternalizePojoToNewJo... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-928) Interceptor that allows invocations only when cluster is formed of N nodes

by Galder Zamarreño (JIRA)

Interceptor that allows invocations only when cluster is formed of N nodes -------------------------------------------------------------------------- Key: ISPN-928 URL: https://issues.jboss.org/browse/ISPN-928 Project: Infinispan Issue Type: Feature Request Components: Configuration, RPC Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final Following from https://github.com/pmuir/infinispan-examples/commit/f5d090092fa7b3660025b... It'd be great to have an configurable StrictCluster interceptor in Infinispan which would basically make all invocations wait until the cluster of N nodes has been formed. I think it'd be a great addition and would allow clients to verify whether the cluster actually forms without the need to verify whether data replicates...etc. In principle, the configuration would be at the CacheManager, i.e.: <transport strictNumMembers="4"... /> However, it could also be useful to configure it at the cache level. So, could maybe want to do this: I want cache X to allow invocations the moment I have 2 nodes (in spite of the cluster being formed of 4 noes), whereas I want cache Y to allow invocations once I have 3 nodes. Apart from an strict number of nodes, you could have a minimum number of nodes: allow invocations once I have 4 or more nodes. The strict value could still be useful to make sure intrusive machines don't get into the cluster, i.e. I expect 4 nodes in the cluster and if I have 5, something is wrong. I think it's an interesting concept that would get rid of cluster validation code in examples and RadarGun. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
4
0 / 0

[JBoss JIRA] (ISPN-2511) org.infinispan.remoting.RemoteExceptionHandlingWithStateTransferTest.testThrowExceptionFromRemoteInterceptor fails randomly

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-2511: ----------------------------------- Summary: org.infinispan.remoting.RemoteExceptionHandlingWithStateTransferTest.testThrowExceptionFromRemoteInterceptor fails randomly Key: ISPN-2511 URL: https://issues.jboss.org/browse/ISPN-2511 Project: Infinispan Issue Type: Bug Reporter: Anna Manukyan Assignee: Mircea Markus https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... The test works properly, when run separately. More logs will be provided later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012