You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2018/02/09 20:20:00 UTC

[jira] [Resolved] (GEODE-4372) RemoteOperationMessage and subclasses are confusing

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

Darrel Schneider resolved GEODE-4372.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

> RemoteOperationMessage and subclasses are confusing
> ---------------------------------------------------
>
>                 Key: GEODE-4372
>                 URL: https://issues.apache.org/jira/browse/GEODE-4372
>             Project: Geode
>          Issue Type: Improvement
>          Components: transactions
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The RemoteOperationMessage is actually part of geode transactions but it is very hard to figure this out by looking at the class. It claims in many places to be part of the implementation of PartitionedRegions but is not. It also throws ForceReattemptException (which should only be done when trying to send a message to a PartitionedRegion bucket) and then does not handle that exception and ends up throwing an InternalGemFireException.
> Action items:
>  # repackage these messages to be in a tx package
>  # remove references to PartitionedRegion in comments
>  # stop throwing ForceReattemptException
>  # change code that uses these messages that is not transactional to use some other message



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