[ 
https://issues.apache.org/jira/browse/GEODE-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971876#comment-15971876
 ] 

Darrel Schneider commented on GEODE-2792:
-----------------------------------------

Here is a refactoring of the code that would fix this:
{code}
  private void concurrencyConfigurationCheck(VersionTag tag) {
    if (this.concurrencyMessageIssued) {
      return;
    }
    boolean serverConcurrencyChecksEnabled = this.concurrencyChecksEnabled;
    boolean clientConcurrencyChecksEnabled = tag != null;
    if (clientConcurrencyChecksEnabled != serverConcurrencyChecksEnabled) {
      this.concurrencyMessageIssued = true;
      logger.info(LocalizedMessage.create(
          
LocalizedStrings.LocalRegion_SERVER_HAS_CONCURRENCY_CHECKS_ENABLED_0_BUT_CLIENT_HAS_1_FOR_REGION_2,
          new Object[] {serverConcurrencyChecksEnabled, 
clientConcurrencyChecksEnabled, this}));
    }
  }
{code}

> Server has concurrencyChecksEnabled log message has the booleans switched
> -------------------------------------------------------------------------
>
>                 Key: GEODE-2792
>                 URL: https://issues.apache.org/jira/browse/GEODE-2792
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Darrel Schneider
>            Priority: Trivial
>
> The log message: "Server has concurrencyChecksEnabled {0} but client has {1}" 
> should instead be:  "Server has concurrencyChecksEnabled {1} but client has 
> {0}".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to