Job scheduler can lose data on forced kill

Details

Description

The page file that keeps the index of jobs to be scheduled is using default write batch size of 1000. That means that index could get into incorrect state when broker is killed (and there's no recovery for this index). Turning off batching (as it's not needed for this low-volume index) will ensure that changes are always persisted immediately.

Issue Links

is duplicated by

AMQ-3818Delayed persistent messages are lost if the broker is hard killed during the delay.