You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/11 18:39:03 UTC

[jira] [Updated] (GEODE-5187) clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl

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

ASF GitHub Bot updated GEODE-5187:
----------------------------------
    Labels: pull-request-available  (was: )

> clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl
> ------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-5187
>                 URL: https://issues.apache.org/jira/browse/GEODE-5187
>             Project: Geode
>          Issue Type: Bug
>          Components: client queues
>            Reporter: Shelley Lynn Hughes-Godfrey
>            Assignee: Shelley Lynn Hughes-Godfrey
>            Priority: Major
>              Labels: pull-request-available
>
> HARegionQueues may have an issue where messages are lost due to the eventId (threadId and sequenceId) being null ... which prevents them from being dispatched to the client.
> This may be due to the ClientUpdateMessageImpl no longer including the eventId when serialized over the wire between servers.  Now the receiving side must use eventId from the HAEventWrapper to re-populate this field in the ClientUpdateMessage. 
> If the null eventId is detected by HARegionQueue.putGIIDataInRegion, the corresponding event is silently dropped.  This occurs when processing the InitialImage of the HARegionQueue from another server.



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