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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.9.0
• Component/s: transactions
• Assignee: Eric Shu
• Reporter: Eric Shu
• Created: 08/Nov/18 01:10
• Updated: 23/Jul/19 16:41
• Resolved: 09/Nov/18 20:21

Description

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.

Issue Links

• is related to: GEODE-7006 Function execution by ID does not have fix for GEODE-6016