[jira] [Closed] (GEODE-7473) when the sender is not ready, before adding to tmpDroppedEvents, should check its destination dsid

["Mark Hanson (Jira)" <ji...@apache.org>]

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

Mark Hanson closed GEODE-7473.
------------------------------

Transition from Resolved to Closed for Apache Geode 1.11.0 RC4 release.

> when the sender is not ready, before adding to tmpDroppedEvents, should check its destination dsid
> --------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7473
>                 URL: https://issues.apache.org/jira/browse/GEODE-7473
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Xiaojian Zhou
>            Priority: Major
>             Fix For: 1.11.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When WAN receiver received an event, if its region also defined a sender, it will check event's GatewaySenderEventCallbackArgument's dsIds to see if it should be  filtered out. 
> WAN used this logic to prevent the event from bouncing back to wrong site, such as original sender. 
> In GEODE-5087's fix, when found sender is not available and add to tmpDroppedEvents before checking event's GatewaySenderEventCallbackArgument. This should be done after checking GatewaySenderEventCallbackArgument.



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