tree 501700860e4b066eedee82e225268b4d05517858
parent 85539771c09ec34126fd03960ac3d242f226ddeb
author Avia Efrat <avia@gigaspaces.com> 1494146578 +0300
committer Avia Efrat <avia@gigaspaces.com> 1494157441 +0300

ARIA-156 Better handle exceptions in the process executor

Previously, if an exception was raised during the starting of a task,
the task's process was permanently blocked on receiving a message.

The reason was that the exception caused the 'listener thread' to
not send a response to the task's process, as the exception was not
handled inside the 'with' block of the listener thread.

The first change I introduced was to wrap the yielding of the message and
the response inside a try-except-finally block, so the exception will be
handled within the 'with' scope, and to ensure a response is sent to the
task's process.

The second change is to move the sending of the 'task started' message in
the task's process to a place where encountering an exception will be
handled via sending a 'task failed' message back to the listener thread.