[
https://issues.apache.org/jira/browse/GEODE-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680676#comment-16680676
]
ASF subversion and git services commented on GEODE-6016:
--------------------------------------------------------
Commit 68b74358a6ce4e9b0ed52e09eafbb80549972003 in geode's branch
refs/heads/feature/GEODE-6016 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=68b7435 ]
GEODE-6016: Make client onRegion function transactional.
* Do not use a function execution thread to send message to server even if
singleHop is enabled when function is in transaction.
* Throw UnsupportedOperationException if client executes onMembers function
using transaction - to behave similar to onServers function when using
transaction.
> 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
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
>
> 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)
