1. I only have this in the log when i reset the scheduler:
2021-02-26 07:02:48.375 +0000 INFO: org.bonitasoft.truckmilk.engine.MilkReportEngine #BonitaCommandAPI TruckMilk.MilkReportEngine: MilkReportEngine ~~ 26/02 07:02:48 Scheduler is started; Schedule reset; Quartz Job Up and running; Heat beat informationLast Heart Beat[undefined], Next[undefined];
And i see this if i reload the page:
2021-02-26 07:06:27.853 +0000 INFO: org.bonitasoft.console.common.server.page.PageResourceServlet This servlet is deprecated. You can now access your resources through their relative URL.see the custom page documentation.
2021-02-26 07:06:28.084 +0000 INFO: org.bonitasoft.command.BonitaCommand BonitaCommand ~~~Verb[GETSTATUS] Tenant[1] Result: in 8 ms
I also found something like this:
2021-02-26 07:10:05.354 +0000 INFO: org.bonitasoft.truckmilk.engine.MilkCmdControl #BonitaCommandAPI TruckMilk.MilkCmdControl: SchedulerStartStop requested[null] -
I did some research, i get #1093 in MySQL, here is a link that explains how i cant select and delete the same table in the same query. A looked at the MySQL docs, this error persists in the later versions of MySQL, in 8.0 this error still exists. Updating the database couldnt help, the reason why it could run in local bonita is because it uses H2 database not MySQL, probably it would work with PostgreSQL. This is what i could come up with after some reasearch :)
https://stackoverflow.com/questions/45494/mysql-error-1093-cant-specify-target-table-for-update-in-from-clause
And this is my query:
delete from arch_process_instance where tenantid = 1 and stateid not in (3,4,6) and not exists (select * from arch_process_instance ar where arch_process_instance.sourceobjectid = ar.sourceobjectid and ar.stateid in (3,4,6)) and not exists (select * from process_instance ar where arch_process_instance.sourceobjectid = ar.id and ar.tenantid=1 ) and id in (1)
2. I used 7.9.0 and then migrated to 7.11.4 (the migration tool said 7.11.0, but we are using 7.11.4 and seem to work fine. The database is something we cant change because we are not the maintainer of it, but it is a MySQL 5.7.33. Maybe we really f.cked up at the beggining. I should add that the heartbeat function worked well, with the database, in Docker Toolbox.
Unfortunately we are not using a subscription model.