[NIFI-2774] ConsumeJMS processor losses messages on NiFi restart

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0, 0.7.0
• Fix Version/s: 1.1.0, 0.7.1
• Component/s: Core Framework
• Assignee: Oleg Zhurakousky
• Reporter: Christopher McDermott
• Created: 14/Sep/16 14:23
• Updated: 11/Oct/16 15:28
• Resolved: 11/Oct/16 15:28

Description

ConsumeJMS processor uses auto-acknowledge mode. Unlike the deprecated GetJMSQueue processor it does not provide a way to specify a different ACK mode (i.e. client-acknowledge.) Using auto-acknowledge, acknowledges message receipt from JMS before the messages are actually added to the flow. This leads to data-loss on NiFi stop (or crash.)

I believe the fix for this is to allow the user to specify the ACK mode in the processor configuration like is allowed by the GetJMSQueue processor.

Issue Links

• duplicates: NIFI-2164 ConsumeJMS should allow user to configure trade-off between 'best effort' and 'guaranteed receipt' of data
• links to: GitHub Pull Request #1022
• links to: GitHub Pull Request #1036