[
https://issues.apache.org/jira/browse/GEODE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807926#comment-16807926
]
Darrel Schneider commented on GEODE-6587:
-----------------------------------------
This failure does not seem to have anything to do with our counters. The test
runs some code on each server checking if it has a txState for a txId. If it
finds one it returns a hard-coded 11. If not it returns a hard-coded 1. So it
expects 11 or 12 because only one server should have returned 11. So in this
new failure when it sees "22" it means that each server had a txState for the
same txId.
> ClientServerTransactionCCEDUnitTest testConnectionAffinity FAILED
> -----------------------------------------------------------------
>
> Key: GEODE-6587
> URL: https://issues.apache.org/jira/browse/GEODE-6587
> Project: Geode
> Issue Type: Bug
> Affects Versions: 1.10.0
> Reporter: xiaojian zhou
> Assignee: Eric Shu
> Priority: Major
>
> It's found in:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/564
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/DistributedTestOpenJDK8/builds/1846
> {noformat}
> org.apache.geode.internal.cache.ClientServerTransactionCCEDUnitTest >
> testConnectionAffinity FAILED
> java.lang.AssertionError: expected count to be 11 or 12 but was 22
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
