elguardian commented on issue #3167: URL: https://github.com/apache/incubator-kie-kogito-runtimes/issues/3167#issuecomment-2757665900
Problem is in here: https://github.com/kiegroup/kogito-runtimes/blob/main/jbpm/jbpm-flow/src/main/java/org/jbpm/workflow/instance/impl/WorkflowProcessInstanceImpl.java#L672 when we are using in memory persistence this is not a big deal as we are dealing with the same object so it synchronize. Problem arise when this is loaded in two different transactions. We have two different objects and we are dealing with two different states in memory objects loaded at the same time. The situation will lead at some point with joins being stuck becuase it cannot compute the triggers. using optimistic lock should work. 1. concurrent hashmap approach won't work. 2. we might need to recover the old locking system mechanism plus version object in database perisstence to cover runtime and clustering environments. -- 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]
