[
https://issues.apache.org/jira/browse/GEODE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808115#comment-16808115
]
Darrel Schneider commented on GEODE-6587:
-----------------------------------------
The cause of this failure is a race in which borrowConnection(ServerLocation)
thinks it is returning a connection to the requested server, but the load
conditioner concurrently change the server that the connection is connected to.
This fix is to do an additional check of the connection's server AFTER it has
been activated. Once activated, the load conditioner is prevented from changing
the server. The concurrency introduced in GEODE-6515 made this race possible.
> 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: Darrel Schneider
> 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)
