Darrel Schneider created GEODE-6613:
---------------------------------------
Summary: ClientServerTransactionFailoverDistributedTest
multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
is flaky
Key: GEODE-6613
URL: https://issues.apache.org/jira/browse/GEODE-6613
Project: Geode
Issue Type: Bug
Components: client/server, transactions
Reporter: Darrel Schneider
ClientServerTransactionFailoverDistributedTest
multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
has recently started failing once in a while.
This may have been caused by: GEODE-6515
When it fails it us because at least one of the transactions changes do not
happen. Here is an example of how it fails:
{noformat}
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$144/1667766308.run
in VM 3 running on Host 671fd56a424e with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
at
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations(ClientServerTransactionFailoverDistributedTest.java:294)
Caused by:
org.junit.ComparisonFailure: expected:<[value1]> but
was:<[originalValue]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverDistributedTest.java:222)
at
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.lambda$multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations$2967fbd$1(ClientServerTransactionFailoverDistributedTest.java:294){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)