Description
I noticed this because when deleteAllMessagesOnStartup was enabled, starting up the JDBC store took a very long time to get started. Digging into it, I noticed that the slow start up was due to trying to clear out the messages after the database lock was aquired. Since the first delete happens before the store is started, and the second the delete happens after the store is started, the second delete is the one giving us the problems with the JDBC store. Going to remove that one.