Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
5.9.0
-
None
Description
Many db log files are kept in the scheduler folder without references in the schedulerDb. It seems like the db log files are kept but should have been deleted.
The environment is configured with mysql message persistence and schedulersupport enabled.
Our folder structure is as follows:
first is:
db-13.log
and then a few other logs:
db-....log
last is:
db-62.log
scheduleDB.data
scheduleDB.redo
Number of messages scheduled: 0.
I think there should only be one db.log file present is this case. Why are there so many db.log files present in the scheduler folder?
The remove method is called from the main schedule loop.
This remove method is called with a timestamp maybe some log files are skipped because of this. When i call the remove method manually all the skipped log files are deleted from the journal.
I've attached the scheduleDB as a zip.