[GEODE-1348] Exceptions thrown from Functions are inconsistently wrapped with FunctionException

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: functions
• Assignee: Unassigned
• Reporter: Dan Smith
• Created: 04/May/16 17:28
• Updated: 04/May/16 17:29

Description

I wrote some tests for how exceptions throw within a function are returned to the executor of the function.

What I'm seeing is that how the function is returned varies based on the topology and region type used. Specifically, in almost all cases an exception thrown from within a Function is wrapped in a FunctionException. But when using onRegion with a partitioned region from an accessor, the exception is not wrapped in a FunctionException but is instead thrown directly.

Exceptions should be handled consistently. Since most cases seem to wrap the exception in a FunctionException, the PR accessor case probably should too.

Issue Links

• is related to: GEODE-625 A function's ResultCollector throws ClassCastException when ResultSender.sendException is invoked