Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
Hi, for the first exception that shows a rollback, what is the root cause exception? There should be a trace in the logs to indicate what the root cause is.
Here is the error of database manager tried to rollback
After the previous error hit, the following activity get another error which is about Duplicate entry of key SHKActivityData
Do you guys have any idea what is the cause the error? It seems like it is something wrong in Joget core code.
1st error looks like something happened during the start process based on the logs. Any changes made to the process? The 2nd one seems like a duplicate id issue. What was done before the error occurred? was there a migration of running processes occurring or something?
Joget version? Database using? Is there any way we can replicate it on our end?
Anyway we actually go did some investigation on the cause of the error. So, when process started new rows will be created in the SHKActivityData table with Unique ID. When the 1st error activity occurs, We suspect the system rollback the value of the Unique ID of SHKActivityData table back to the value before that error activity was ran. However, the error activity had created new rows in the SHKActivityData table but these rows are not deleted during the rollback.
Due to above error, the following process get the duplicate issue after started since system will try to create new rows in SHKActivityData table using the rollbacked Unique ID and get our second error where tell us duplicate ID issue.
We also found that the Unique ID in the SHKActivityData will still auto increased by one after the second error hit. Based on the first error, the system roll backed with a count of 10. So, there is a total of 10 following process in our Joget hit the second error. On the 11th process and onwards, process is normal and didnt hit the second error anymore.