November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3725) useSynchronization="false" and versioningScheme="SIMPLE" don't work together

by Radim Vansa (JIRA)

Radim Vansa created ISPN-3725: --------------------------------- Summary: useSynchronization="false" and versioningScheme="SIMPLE" don't work together Key: ISPN-3725 URL: https://issues.jboss.org/browse/ISPN-3725 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 6.0.0.CR1 Reporter: Radim Vansa Assignee: Mircea Markus It seems like this combination is unexpected (see stacktrace below) However, writeSkewCheck requires SIMPLE versioning scheme. {code} java.lang.ClassCastException: org.infinispan.container.versioning.SimpleClusteredVersion cannot be cast to org.infinispan.container.versioning.NumericVersion at org.infinispan.transaction.xa.TransactionFactory$TxFactoryEnum$4.newGlobalTransaction(TransactionFactory.java:140) at org.infinispan.transaction.xa.TransactionFactory.newGlobalTransaction(TransactionFactory.java:245) at org.infinispan.transaction.TransactionTable.getOrCreateLocalTransaction(TransactionTable.java:319) at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:277) at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:240) at org.infinispan.interceptors.TxInterceptor.visitPutKeyValueCommand(TxInterceptor.java:186) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:112) at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) at org.infinispan.statetransfer.StateTransferInterceptor.handleNonTxWriteCommand(StateTransferInterceptor.java:197) at org.infinispan.statetransfer.StateTransferInterceptor.visitPutKeyValueCommand(StateTransferInterceptor.java:132) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) at org.infinispan.interceptors.CacheMgmtInterceptor.updateStoreStatistics(CacheMgmtInterceptor.java:148) at org.infinispan.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:134) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:106) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:70) at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:321) at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1296) at org.infinispan.CacheImpl.putInternal(CacheImpl.java:869) at org.infinispan.CacheImpl.put(CacheImpl.java:861) at org.infinispan.CacheImpl.put(CacheImpl.java:1349) at org.infinispan.CacheImpl.put(CacheImpl.java:206) at org.radargun.cachewrappers.InfinispanBasicOperations.put(InfinispanBasicOperations.java:25) at org.radargun.cachewrappers.Infinispan51BasicOperations.put(Infinispan51BasicOperations.java:31) at org.radargun.cachewrappers.Infinispan52BasicOperations.put(Infinispan52BasicOperations.java:16) at org.radargun.cachewrappers.InfinispanWrapper.put(InfinispanWrapper.java:184) at org.radargun.stages.ClusterValidationStage.tryToPut(ClusterValidationStage.java:137) at org.radargun.stages.ClusterValidationStage.checkReplicationSeveralTimes(ClusterValidationStage.java:149) at org.radargun.stages.ClusterValidationStage.executeOnSlave(ClusterValidationStage.java:58) at org.radargun.Slave$2.run(Slave.java:103) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) {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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3724: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> made a comment on [bug 1031660|https://bugzilla.redhat.com/show_bug.cgi?id=1031660] Please, see linked JIRA. > REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60) > ------------------------------------------------------------------------------------------- > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > Put entry to the SOURCE node. > Start TARGET node, specifying source node as a REST RCS. > Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60 > Please, see full stack trace in attached file. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3723) REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3723?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-3723: ------------------------------------ might be connected to: https://issues.jboss.org/browse/ISPN-3724 > REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException) > --------------------------------------------------------------------------------------------- > > Key: ISPN-3723 > URL: https://issues.jboss.org/browse/ISPN-3723 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: restRollUpsPersistenceExceptionCantMigrate > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > 20 entries stored on source node successfully, > recordKnownGlobalKeySet does not nothing (this is ok) REST is able to provide full key set > but then, > operation "synchronizeData" using "rest" issued on new node is returning: > 14:05:23,252 INFO [org.infinispan.upgrade.RollingUpgradeManager] (pool-1-thread-1) ISPN000216: 0 entries migrated to cache default in 30 milliseconds > however, there is 20 entries stored in the old node. > Please see attached file for more detailed stack trace. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-3724: ------------------------------------ might be connected to: https://issues.jboss.org/browse/ISPN-3723 > REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60) > ------------------------------------------------------------------------------------------- > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > Put entry to the SOURCE node. > Start TARGET node, specifying source node as a REST RCS. > Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60 > Please, see full stack trace in attached file. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] Tomas Sykora edited comment on ISPN-3724 at 11/18/13 8:32 AM: -------------------------------------------------------------- Attached server output when trying to fetch entry from "old" RCS was (Author: tsykora): server output when trying to fetch entry from "old" RCS > REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60) > ------------------------------------------------------------------------------------------- > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > Put entry to the SOURCE node. > Start TARGET node, specifying source node as a REST RCS. > Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60 > Please, see full stack trace in attached file. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3723) REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3723?page=com.atlassian.jira.plugin.... ] Tomas Sykora edited comment on ISPN-3723 at 11/18/13 8:32 AM: -------------------------------------------------------------- Attached server output file was (Author: tsykora): server output > REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException) > --------------------------------------------------------------------------------------------- > > Key: ISPN-3723 > URL: https://issues.jboss.org/browse/ISPN-3723 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: restRollUpsPersistenceExceptionCantMigrate > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > 20 entries stored on source node successfully, > recordKnownGlobalKeySet does not nothing (this is ok) REST is able to provide full key set > but then, > operation "synchronizeData" using "rest" issued on new node is returning: > 14:05:23,252 INFO [org.infinispan.upgrade.RollingUpgradeManager] (pool-1-thread-1) ISPN000216: 0 entries migrated to cache default in 30 milliseconds > however, there is 20 entries stored in the old node. > Please see attached file for more detailed stack trace. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3724: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1031660 > REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60) > ------------------------------------------------------------------------------------------- > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > Put entry to the SOURCE node. > Start TARGET node, specifying source node as a REST RCS. > Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60 > Please, see full stack trace in attached file. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-3724: ------------------------------- Attachment: RestRollUpsUnsupportedProtocol60 server output when trying to fetch entry from "old" RCS > REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60) > ------------------------------------------------------------------------------------------- > > Key: ISPN-3724 > URL: https://issues.jboss.org/browse/ISPN-3724 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: RestRollUpsUnsupportedProtocol60 > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > Put entry to the SOURCE node. > Start TARGET node, specifying source node as a REST RCS. > Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60 > Please, see full stack trace in attached file. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3724) REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60)

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-3724: ---------------------------------- Summary: REST RollUps 5.2.4 to 6.0.0 -- target can't fetch entries (Unsupported protocol version 60) Key: ISPN-3724 URL: https://issues.jboss.org/browse/ISPN-3724 Project: Infinispan Issue Type: Bug Affects Versions: 6.0.0.CR1 Reporter: Tomas Sykora Assignee: Mircea Markus Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. Put entry to the SOURCE node. Start TARGET node, specifying source node as a REST RCS. Calling get on the TARGET node will cause PersistenceException caused by Caused by: java.io.IOException: Unsupported protocol version 60 Please, see full stack trace in attached file. -- 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 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3723) REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3723?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3723: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> made a comment on [bug 1031656|https://bugzilla.redhat.com/show_bug.cgi?id=1031656] See linked JIRA > REST RollUps from 5.2.4 to 6.0.0 -- migrates 0 entries (probably due to PersistenceException) > --------------------------------------------------------------------------------------------- > > Key: ISPN-3723 > URL: https://issues.jboss.org/browse/ISPN-3723 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Attachments: restRollUpsPersistenceExceptionCantMigrate > > > Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and old 5.2.4 server (jdg 6.1.GA) as a source node. > 20 entries stored on source node successfully, > recordKnownGlobalKeySet does not nothing (this is ok) REST is able to provide full key set > but then, > operation "synchronizeData" using "rest" issued on new node is returning: > 14:05:23,252 INFO [org.infinispan.upgrade.RollingUpgradeManager] (pool-1-thread-1) ISPN000216: 0 entries migrated to cache default in 30 milliseconds > however, there is 20 entries stored in the old node. > Please see attached file for more detailed stack trace. -- 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 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 November 2013