-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Regression] Terminate end events - Command 'COMPLETE' rejected with code 'PROCESSING_ERROR' #876
Comments
Team triage:
|
Another reproducible example is provided in #893 |
Has there been triaging of this issue? We'd like to know if it's a problem on our end of an acknowledged (potentially serious) bug in the testing library or zeebe. |
Thanks for reaching out again @namero999. I can confirm that this is not an issue in Zeebe. There appears to be bug in the in memory transaction management of this library. I haven't quite pinpointed it yet, but I hope this lowers your concerns. |
Just found the problem and created a PR to fix it. It'll be part of the next patch releases ( |
933: Backport 876 to stable/8.2 r=nicpuppa a=remcowesterhoud #876 Co-authored-by: Remco Westerhoud <[email protected]>
934: Backport 876 to stable/8.1 r=nicpuppa a=remcowesterhoud #876 Co-authored-by: Remco Westerhoud <[email protected]>
932: Backport 876 stable/8.3 r=nicpuppa a=remcowesterhoud #876 Co-authored-by: Remco Westerhoud <[email protected]>
There seems to be an issue with
terminate
end events and multiple tokens.This test (code below) passes with 8.1.8 but fails with 8.2.12
The BPMN starts with a parallel gateway, with a token waiting for a timeout to expire while the rest of the process continues. Both end events are terminate events. The issue seems related to the presence of terminate events and multiple tokens in the process, because commenting out the "timeout" branch makes the test pass with 8.2.12 as well.
The issue arises when completing the last service task before the terminate end event.
Test code
Process
Environment
The text was updated successfully, but these errors were encountered: