Closed ghost closed 9 years ago
After a while, database size is considerably increased because of the output messages & stack traces stored in database.
Should an option be added to automatically delete old jobs? For instance keep history for up to 1 week.
If bundle won't handle this itself, a recurring command needs to be created by developers who use this bundle.
Looks like jms-job-queue:clean-up command does what you want.
After a while, database size is considerably increased because of the output messages & stack traces stored in database.
Should an option be added to automatically delete old jobs? For instance keep history for up to 1 week.
If bundle won't handle this itself, a recurring command needs to be created by developers who use this bundle.