Ivan Godwin created GEODE-7871:
----------------------------------

             Summary: CI Failure: 
ClientServerHostNameVerificationDistributedTest.expectConnectionFailureWhenNoHostNameInLocatorKey
 Failed
                 Key: GEODE-7871
                 URL: https://issues.apache.org/jira/browse/GEODE-7871
             Project: Geode
          Issue Type: Bug
            Reporter: Ivan Godwin


ClientServerHostNameVerificationDistributedTest > 
expectConnectionFailureWhenNoHostNameInLocatorKey failed with the following 
output:


{code:java}
org.apache.geode.cache.client.internal.ClientServerHostNameVerificationDistributedTest
 > expectConnectionFailureWhenNoHostNameInLocatorKey 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 3602

    [fatal 2020/03/12 02:42:26.780 GMT <unused p2p reader> tid=94] Uncaught 
exception in thread Thread[unused p2p reader,5,RMI Runtime]
    org.apache.geode.distributed.DistributedSystemDisconnectedException: 
Distribution manager on 172.17.0.14(server-2:95)<v2>:41002 started at Thu Mar 
12 02:42:11 GMT 2020: Message distribution has terminated
        at 
org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2872)
        at 
org.apache.geode.internal.tcp.TCPConduit$Stopper.generateCancelledException(TCPConduit.java:1004)
        at 
org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
        at 
org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1666)
        at org.apache.geode.internal.tcp.Connection.run(Connection.java:1446)
        at java.base/java.lang.Thread.run(Thread.java:834)

{code}
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1621



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

Reply via email to