geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GEODE-6932) Suspect string in WANRollingUpgradeNewSenderProcessOldEvent
Date Tue, 02 Jul 2019 23:13:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Smith reassigned GEODE-6932:
--------------------------------

    Assignee: Dan Smith

> Suspect string in WANRollingUpgradeNewSenderProcessOldEvent
> -----------------------------------------------------------
>
>                 Key: GEODE-6932
>                 URL: https://issues.apache.org/jira/browse/GEODE-6932
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>            Priority: Major
>
> 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
>     java.io.EOFException: Locator at 37cf66d2d62e/172.17.0.13:28019 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
(v7.6.3#76005)

Mime
View raw message