NguyenDinhThien-future-aavn commented on PR #4003: URL: https://github.com/apache/incubator-kie-kogito-runtimes/pull/4003#issuecomment-3173484324
@fjtirado I tried throwing exception if the process instance is not active in ProcessEventDispatcher, or ProcessServiceImpl, but both places do not seem to resolve the problem completely. <img width="569" height="1201" alt="3podsstillissue (Page 1)" src="https://github.com/user-attachments/assets/663d173c-3e15-460a-9df4-ba57f1a982eb"; /> What I mean by that is, for example in the attached image, if the request to start the process instance was sent from pod 1, and pod 2 receives the callback event for the same process instance, my fix can make pod 2 non-ack the event and respond with an error, and when the callback event is resent/retried by the broker to pod 2, pod 2 can properly handle the event and publish another message (of the next state in the workflow) to the broker. Pod 3 then receives the callback event, but it does not transition to the next state of the workflow by publishing another message for the next state, and the event is still consumed, properly because the process instance is active. But if it is active, why doesn't it do the next work? So maybe this pull request does not make sense anymore since I am not able to resolve the problem completely. Therefore I think I will close this pull request, and for the time being, try to live with the problems. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
