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

Shelley Lynn Hughes-Godfrey commented on GEODE-4165:
----------------------------------------------------

This failure reproduced during ci ... the extra logging shows that this is the 
same issue we see in GEODE-4144 (the port portion of the membershipId is 0 in 
the member initiating the operation, but has the correct port number in members 
receiving the distributed event:
{noformat}
[vm0] [warn 2018/01/05 21:07:47.024 UTC <ServerConnection on port 21054 Thread 
2> tid=0x86] Expected 
EventID[172.17.0.8(:loner):0:658e26c8;threadID=2;sequenceID=0], but processed
EventID[172.17.0.8(:loner):53296:658e26c8;threadID=2;sequenceID=0]
{noformat}

> Test failed to get proper event id during a region clear
> --------------------------------------------------------
>
>                 Key: GEODE-4165
>                 URL: https://issues.apache.org/jira/browse/GEODE-4165
>             Project: Geode
>          Issue Type: Bug
>          Components: client queues
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Brian Rowe
>
> This occurred during a run of  
> EventIDVerificationDUnitTest.testEventIDPrapogationOnServerDuringRegionClear. 
>  The stack trace for this one isn't really helpful:
> org.apache.geode.internal.cache.tier.sockets.EventIDVerificationDUnitTest > 
> testEventIDPrapogationOnServerDuringRegionClear FAILED
>     java.lang.AssertionError
>         at org.junit.Assert.fail(Assert.java:86)
>         at org.junit.Assert.assertTrue(Assert.java:41)
>         at org.junit.Assert.assertTrue(Assert.java:52)
>         at 
> org.apache.geode.internal.cache.tier.sockets.EventIDVerificationDUnitTest.testEventIDPrapogationOnServerDuringRegionClear(EventIDVerificationDUnitTest.java:150)
> It's unclear what happened here and I was unable to reproduce this failure 
> with 500 retries.  The test output also didn't contain any relevant data and 
> matched the successful runs (at least for stdout, it doesn't look like stderr 
> was captured here).  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to