You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Alexander Murmann (Jira)" <ji...@apache.org> on 2020/08/04 21:36:00 UTC

[jira] [Resolved] (GEODE-6100) LogConsumer is creating instability in suspect string detection

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

Alexander Murmann resolved GEODE-6100.
--------------------------------------
    Resolution: Fixed

looks like a PR addressed this already

> LogConsumer is creating instability in suspect string detection
> ---------------------------------------------------------------
>
>                 Key: GEODE-6100
>                 URL: https://issues.apache.org/jira/browse/GEODE-6100
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Patrick Rhomberg
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> (Original ticket title: CI: CacheClientNotifierDUnitTest.testNormalClient2MultipleCacheServer failed with suspect strings)
> Failure at:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/163
> Failed with message:
> {noformat}
> org.apache.geode.internal.cache.wan.CacheClientNotifierDUnitTest > testNormalClient2MultipleCacheServer 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 3689
>       /hom[warn 2018/11/27 21:24:25.124 UTC <queueTimer-testNormalClient2MultipleCacheServer_PR1> tid=179] Cache Client Updater Thread  on ef956df2d60b(376)<v1>:41003 port 28307 (ef956df2d60b:28307): Caught following exception while attempting to create a server-to-client communication socket and will exit: org.apache.geode.cache.client.ServerRefusedConnectionException: <null inet_addr hostname><ec>:28307 refused connection: A previous connection attempt from this client is still being processed: identity(172.17.0.8(381:loner):47756:85080f57,connection=1
> {noformat}
> Results viewable at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.198/test-results/distributedTest/1543356956/
> Artifacts available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.198/test-artifacts/1543356956/distributedtestfiles-OpenJDK8-1.9.0-build.198.tgz
> Possibly related to GEODE-5595 per the comment by Ken Howe, insofar as his comment also includes the same suspect string.  Also quite possibly unrelated.  You, dear reader, can find out!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)