geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-6932) Suspect string in WANRollingUpgradeNewSenderProcessOldEvent
Date Wed, 03 Jul 2019 18:23:00 GMT


ASF subversion and git services commented on GEODE-6932:

Commit 15ad204e3c5fff440face5e8370b7451c4be6fff in geode's branch refs/heads/develop from
Dan Smith
[;h=15ad204 ]

GEODE-6932: Ignoring log message about locator bouncing

Ignoring an log message about the locator being restarted in
WANRollingUpgradeNewSenderProcessOldEvent. These tests are upgrading the

> Suspect string in WANRollingUpgradeNewSenderProcessOldEvent
> -----------------------------------------------------------
>                 Key: GEODE-6932
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
> This test failed with a suspect string in CI. Looking at the test, it looks like we should
just expect this error message, the test is bouncing locators and if the client tries to contact
the locator that the wrong time it will log this info message.
> {noformat}
> org.apache.geode.cache.wan.WANRollingUpgradeNewSenderProcessOldEvent > oldEventShouldBeProcessedAtNewSender[from_v100] FAILED
>     java.lang.AssertionError: Suspicious strings were written to the log during this run.
>     Fix the strings or use IgnoredException.addIgnoredException to ignore.
>     -----------------------------------------------------------------------
>     Found suspect string in log4j at line 4117
> Locator at 37cf66d2d62e/ did not respond. This is normal if the locator was shutdown. If it wasn't check its log for exceptions.{noformat}

This message was sent by Atlassian JIRA

View raw message