-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught BPMN Error leads to NullPointerException in OutputMapping on External Task #2643
Comments
This comment was imported from JIRA and written by user @ThorbenLindhauer Test case: https://github.com/camunda/camunda-bpm-platform/compare/CAM-13325-uncaught-error-extTask |
This comment was imported from JIRA and written by user @ThorbenLindhauer An idea for a fix could be to set the activity to null before calling process end. I pushed this to the branch: 14e85aa Then 25 test cases fail:
Full list of failures:
|
This issue was imported from JIRA:
Environment (Required on creation):
skipOutputMappingOnCanceledActivities
is set totrue
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
Steps to reproduce (Required on creation):
Observed Behavior (Required on creation):
Expected behavior (Required on creation):
Root Cause (Required on prioritization):
ExecutionEntity#destroy
- when the process instance is destroyed. The output parameter is executed twice: once when scope execution of the activity with the mapping is destroyed (=> expected) and once when the process instance execution is destroyed (=> not expected)PvmAtomicOperationActivityEnd
sets the activity on the next higher execution after removal (https://github.com/camunda/camunda-bpm-platform/blob/7.14.0/engine/src/main/java/org/camunda/bpm/engine/impl/pvm/runtime/operation/PvmAtomicOperationActivityEnd.java#L66)Solution Ideas (Optional):
Hints (Optional):
Links:
The text was updated successfully, but these errors were encountered: