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

Dan Smith resolved GEODE-6932.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

> 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
>             Fix For: 1.10.0
>
>          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
>     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)

Reply via email to