Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-4924

Proper handling of invalid messages in SNF queues

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.35.0
    • None
    • Clustering
    • None

    Description

      Currently, if a poison message missing queue information ends up in the SF queue, the broker logs an error, like:

      AMQ222110: no queue IDs defined...

      but the message remains in the queue, with the result that the bridge continuously reconnects, encounters the failure, then evicts the bridge consumer.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. ARTEMIS-5140 Poisonous message in $.artemis.internal queue causes high resource usage on target redistribution node in cluster

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

          Web Link GitHub Pull Request #5091

          Activity

            People

              gaohoward Howard Gao
              gaohoward Howard Gao
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

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