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

ConsumeJMS should handle any message type

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.11.0
    • Component/s: Extensions
    • Labels:
      None

      Description

      At the moment ConsumeJMS only handles TextMessage and ByteMessage. Support for StreamMessage, ObjectMessage and MapMessage should be added. Besides, there could be additional message types implementing the interface like ActiveMQBlobMessage.

      Supporting this would require extra work as this depends of the JMS providers. A property ERROR_QUEUE should be added to re-route the messages into another queue when there is no way to process the messages in the processor so that unsupported and/or malformed messages are still acknowledged and moved somewhere else without further blocking message processing.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tpalfy Tamas Palfy
                Reporter:
                pvillard Pierre Villard
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m