elguardian commented on issue #597: URL: https://github.com/apache/incubator-kie-issues/issues/597#issuecomment-1746477786
OK. I have a possible explanation for this. https://github.com/kiegroup/jbpm/blob/main/jbpm-runtime-manager/src/main/java/org/jbpm/runtime/manager/impl/migration/MigrationManager.java#L693-L698 This code requires that the timers are being registered in memory as this flag is set -Dorg.jbpm.timer.disableUnmarshallerRegistration=true the migration process does not load the timers in the system that is being used cause the timer map not being found in the node and therefore not being canceled. As the rest of the system is being migrated the timers fires in the old container causing the session not found. Funny enough we should see some warnings in the report. What I need to understand is 2 things. 1. The flag was set before the TimerMappingInfo table or not 2. that flag should not be needed. this is not logged but the outcome of hte migration report. -- 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]
