When consumers that utilize an aggregation store are set up for failover (exclusive consumer configuration), a leveldb repository is desired as an alternative to a JDBC store. Currently, when the second consumer attempts to connect to the leveldb store, it cannot obtain the lock on the database and the camel route fails/shuts down. Desired behavior is for the second consumer to connect to the aggregation repository, wait to become the exclusive consumer, and then start processing aggregations.