geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murtuza Boxwala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-6936) WANRollingUpgradeNewSenderProcessOldEvent > bothOldAndNewEventsShouldBeProcessedByOldSender CI failure
Date Wed, 03 Jul 2019 21:25:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878170#comment-16878170
] 

Murtuza Boxwala commented on GEODE-6936:
----------------------------------------

[https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/UpgradeTestOpenJDK8/builds/754]

> WANRollingUpgradeNewSenderProcessOldEvent > bothOldAndNewEventsShouldBeProcessedByOldSender
CI failure
> ------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6936
>                 URL: https://issues.apache.org/jira/browse/GEODE-6936
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Murtuza Boxwala
>            Priority: Major
>
> This might not actually be a failure if the locator was expectedly shut down during
the test run:
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeNewSenderProcessOldEvent > bothOldAndNewEventsShouldBeProcessedByOldSender[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 4485 /home/geode/.gradle/caches/module[info 2019/07/03
18:45:13.006 GMT <poolTimer-DEFAULT-6> tid=0x3f] Communication with locator 17207b1116c4/172.17.0.30:26712
failed with java.io.EOFException: Locator at 17207b1116c4/172.17.0.30:26712 did not respond.
This is normal if the locator was shutdown. If it wasn't check its log for exceptions.. java.io.EOFException:
Locator at 17207b1116c4/172.17.0.30:26712 did not respond. This is normal if the locator was
shutdown. If it wasn't check its log for exceptions. at org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:202)
at org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:130)
at org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:193)
at org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:225)
at org.apache.geode.cache.client.internal.AutoConnectionSourceImpl$UpdateLocatorListTask.run2(AutoConnectionSourceImpl.java:379)
at org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1235) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:256)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message