NguyenDinhThien-future-aavn commented on PR #4003: URL: https://github.com/apache/incubator-kie-kogito-runtimes/pull/4003#issuecomment-3139013312
> @NguyenDinhThien-future-aavn thanks for your contribution, could you add also some tests to cover the scenarios you're treating? Yup, I'm trying to add some tests. But after testing manually again, I don't think this resolves completely the issues that I'm having with callback events reaching different pods. <img width="569" height="1201" alt="3podsstillissue (Page 1)" src="https://github.com/user-attachments/assets/498afd40-7268-43e7-a57f-53c1cb7fb282"; /> 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? Therefore, I think that I might be fixing at the wrong place in the code base, and as I'm brand new to this project, I'm kinda overwhelmed since it is huge. Do you have any hints to whether the current places I modified are the right places to resolve this issue? -- 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]
