Uploaded image for project: 'A-MQ Broker'
  1. A-MQ Broker
  2. ENTMQBR-185

Broker throws NPE on on flow frames for invalid selectors

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: A-MQ 7.0.0.ER9
    • Fix Version/s: A-MQ 7.0.0.ER14
    • Component/s: None
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide

      Run ftest3.cpp

      Show
      Run ftest3.cpp
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      In previous versions of the product, using a malformed selector or filter with an AMQP client would cause the broker to throw an exception and the client would not work.

      This issue has been resolved in this release.
      Show
      In previous versions of the product, using a malformed selector or filter with an AMQP client would cause the broker to throw an exception and the client would not work. This issue has been resolved in this release.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      When a malformed selector string is provided on a link, the broker
      throws NPE on flow frames from the client. In the case of a drain
      request, the drain handshake never completes and the client hangs.

      Presumably the link attach should fail complaining about the selector.

      The bad selector in the attached ftest.cpp is "NULL = 'uH0VZlSY'".

      Other selectors causing NPEs from ENTMQCL-320 are:

      "a IN ( 8, 7 )"
      "a IN ( x, y, z )"
      "1a = 'i7CzIyqt'"

        Gliffy Diagrams

          Attachments

          1. ftest3_ses
            6 kB
          2. ftest3.cpp
            1 kB

            Issue Links

              Activity

                People

                • Assignee:
                  ataylor Andy Taylor
                  Reporter:
                  cliffjansen Cliff Jansen
                  Tester:
                  David Kornel
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: