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

Incorrect message priority displayed in hawtio console

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: AMQ 7.0.3.GA
    • Fix Version/s: AMQ 7.2.0.GA
    • Component/s: console
    • Environment:

      Red Hat AMQ 7

    • Target Release:
    • Affects:
      Release Notes
    • Release Notes Text:
      When viewing messages in AMQ Console, the message priority is now correct. Before, the message priority incorrectly defaulted to 4.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      When a message with priority 6 is send through nodej and java script the brows operation in hawtio console displays the message with incorrect priority i.e 4. But if listMessages operation is called it displays the message with correct priority of 6 (see attached screen shots)

        Gliffy Diagrams

          Attachments

          1. browse.jpeg
            browse.jpeg
            429 kB
          2. listMessages.jpeg
            listMessages.jpeg
            491 kB
          3. screenshot-1.png
            screenshot-1.png
            14 kB
          4. screenshot-2.png
            screenshot-2.png
            30 kB
          5. Snímek z 2018-01-30 09-43-14.png
            Snímek z 2018-01-30 09-43-14.png
            30 kB
          6. Snímek z 2018-01-30 09-43-32.png
            Snímek z 2018-01-30 09-43-32.png
            16 kB

            Issue Links

              Activity

                People

                • Assignee:
                  sknot Stanislav Knot
                  Reporter:
                  raggz Tom Ross
                  Tester:
                  Oleg Sushchenko
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: