[AMQ-3801] Job scheduler can lose data on forced kill

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0
• Assignee: Dejan Bosanac
• Reporter: Dejan Bosanac
• Created: 05/Apr/12 11:35
• Updated: 06/May/13 19:59
• Resolved: 05/Apr/12 11:36

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-3818 Delayed persistent messages are lost if the broker is hard killed during the delay.