[
https://issues.jboss.org/browse/ISPN-4200?page=com.atlassian.jira.plugin....
]
Tomas Sykora commented on ISPN-4200:
------------------------------------
This really might be affected by the fact, that (for this test) compatibility mode is
enabled on both: new and old server.
^ I used CLI for my former investigation, but it looks like we ALSO have a bug in CLI
codec encoder for REST.
It looks like 2 different issues actually.
"Pure" REST rolling upgrades (using REST Helper) are working fine, so
compatibility or/and accessing cache not using REST Helper in this example config test has
to affect behaviour.
We need to look on it closely.
ExampleConfigsTest.testRestRollingUpgrades fails
------------------------------------------------
Key: ISPN-4200
URL:
https://issues.jboss.org/browse/ISPN-4200
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite - Server
Reporter: Jakub Markos
Assignee: Mircea Markus
Fails in the latest snapshot on line 240 with
{code}
Can't access etries stored in source node (target's RestCacheStore).
expected:<value1> but was:<[B@19676adb>
{code}
you can run the test from /server/integration/testsuite with this command:
mvn clean test -Psuite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades
The configs used are
/server/integration/testsuite/target/server/node1/standalone/configuration/examples/{standalone-rest-rolling-upgrade.xml,
standalone-compatibility-mode.xml}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)