[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909344#comment-16909344
]
ASF subversion and git services commented on GEODE-6613:
Commit e5540724ea9000b789c01d4073504f84b191e055 in geode's branch
refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e554072 ]
GEODE-6613: Do not set TransactionTimeout in the test. (#3934)
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.14#76016)
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908593#comment-16908593
]
Bill Burcham commented on GEODE-6613:
-
happened again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/984
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.14#76016)
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908472#comment-16908472
]
ASF subversion and git services commented on GEODE-6613:
Commit 667b836ae1dbd81536dbad20d1ca3adbcc87 in geode's branch
refs/heads/feature/GEODE-6613 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=667b836 ]
GEODE-6613: Do not set TransactionTimeout in the test.
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
>
> 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.14#76016)
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908460#comment-16908460
]
Eric Shu commented on GEODE-6613:
-
This is caused by transaction expired due to resource issue -- (in-between op
is longer than the 4 seconds set in the test).
[vm0] [info 2019/08/08 18:40:54.053 GMT
tid=0x20] Received method:
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877.run
with 0 args on object:
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877@6f4ed7f2
[vm0] [warn 2019/08/08 18:40:54.055 GMT
tid=0x20] ClientHealthMonitor: Unregistering client with member id
identity(172.17.0.5(1:loner):40276:5da48872,connection=1 due to: Unknown reason
[vm0] [info 2019/08/08 18:40:54.057 GMT
tid=0x20] Got result: null
[vm0] from
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877.run
with 0 args on object:
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877@6f4ed7f2
(took 2 ms)
[warn 2019/08/08 18:40:59.398 GMT tid=0x48] Statistics sampling
thread detected a wakeup delay of 3375 ms, indicating a possible resource
issue. Check the GC, memory, and CPU statistics.
[vm1] [warn 2019/08/08 18:40:59.412 GMT tid=0x45] Statistics
sampling thread detected a wakeup delay of 3679 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[vm3] [warn 2019/08/08 18:40:59.031 GMT tid=0x40] Statistics
sampling thread detected a wakeup delay of 3318 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[vm2] [warn 2019/08/08 18:40:59.556 GMT tid=0x49] Statistics
sampling thread detected a wakeup delay of 3819 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[locator] [warn 2019/08/08 18:40:59.267 GMT tid=0x3a] Statistics
sampling thread detected a wakeup delay of 3713 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[vm0] [warn 2019/08/08 18:40:59.636 GMT tid=0x42] Statistics
sampling thread detected a wakeup delay of 4003 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[warn 2019/08/08 18:40:59.978 GMT tid=0x64] Pool unexpected closed
socket on server connection=Pooled Connection to 8227e70436f0:41843:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
[warn 2019/08/08 18:40:59.984 GMT tid=0x69] Pool unexpected closed
socket on server connection=Pooled Connection to 8227e70436f0:41843:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
[warn 2019/08/08 18:40:59.988 GMT tid=0x62] Pool unexpected closed
socket on server connection=Pooled Connection to 8227e70436f0:41843:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
>
> 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
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903255#comment-16903255
]
Juan José Ramos Cassella commented on GEODE-6613:
-
*The test failed again in CI run 973:*
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/973]
*Test Results URI:*
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0017/test-results/distributedTest/1565291849/]
*Test report artifacts from the failed job:*
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0017/test-artifacts/1565291849/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0017.tgz]
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: flaky
>
> 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.14#76016)
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902934#comment-16902934
]
Juan José Ramos Cassella commented on GEODE-6613:
-
*The test failed again in CI run 968:*
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/968
*Test Results URI:*
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0015/test-results/distributedTest/1565231839/
*Test report artifacts from the failed job:*
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0015/test-artifacts/1565231839/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0015.tgz
> 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
>Assignee: Darrel Schneider
>Priority: Major
> Labels: flaky
>
> 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.14#76016)
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902932#comment-16902932
]
Juan José Ramos Cassella commented on GEODE-6613:
-
*The test failed again in CI run 970:*
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/970].
*Test Results URI:*
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0015/test-results/distributedTest/1565253439/]
*Test report artifacts from the failed job:*
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0015/test-artifacts/1565253439/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0015.tgz].
> 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
>Assignee: Darrel Schneider
>Priority: Major
> Labels: flaky
>
> 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.14#76016)
