Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-2774

ConsumeJMS processor losses messages on NiFi restart

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.0.0, 0.7.0
    • 1.1.0, 0.7.1
    • Core Framework
    • None

    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.

      Attachments

        1. 2774.patch
          5 kB
          Christopher McDermott

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. NIFI-2164 ConsumeJMS should allow user to configure trade-off between 'best effort' and 'guaranteed receipt' of data

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #1022

          Web Link GitHub Pull Request #1036

          Activity

            People

              ozhurakousky Oleg Zhurakousky
              chris@mcdermott.net Christopher McDermott
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: