[jira] [Updated] (GEODE-6016) Geode function execution in client transaction with singleHopEnabled is not transactional

["Eric Shu (JIRA)" <ji...@apache.org>]

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

Eric Shu updated GEODE-6016:
----------------------------
    Affects Version/s: 1.1.0

> Geode function execution in client transaction with singleHopEnabled is not transactional
> -----------------------------------------------------------------------------------------
>
>                 Key: GEODE-6016
>                 URL: https://issues.apache.org/jira/browse/GEODE-6016
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: 1.1.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>             Fix For: 1.9.0
>
>
> When function execution with single hop enabled, a function execution thread will execute the function. The function execution thread does not send a transactional message to server and this causes the function execution non transactional.
> This occurs when txmanager.begin is invoked on client like the following:
> txManager.begin();
> ResultCollector resultCollector = execution.withFilter(keySet).execute(function); resultCollector.getResult();
> txManager.commit()/rollback();
> If txmanager.begin() is embedded in function body, there is no issue as transaction starts on server directly.



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