Change how we dequeue messages and manually flag Active MQ when we finish dequing a batch of messages.
The current processs is as follows
1. Nifi will batch up messages and send to JMS
2. Ops Manager (ProvenanceEventReceiver.java) will listen for those messages via JMS and dequeue them and then start inserting/processing the records.
If Ops manager goes down between the time the messages were dequeued and before they were inserted into the database, that provenance history is lost.
See if we can change ActiveMQ from auto dequeing to have it programmatically set the flag saying this payload was dequeued.
Migrate from: PC-621
fixed with spring jms session transaction