Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-5036

[Java Broker] View Message dialog fails to display persistance and expiration info

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.18, 0.20, 0.22
    • Fix Version/s: 0.24, 0.25
    • Component/s: Java Broker
    • Labels:
      None

      Description

      In the 'View Message' dialog in the web management console, messages always display as "Persistent: True" regardless of their actual persistence setting.

      Similarly, messages set with an expiration time display no value against the "Expiration" field.

      In the case of the latter, this looks to be a mismatch between the IDs in the attribute name in the JSON, and the HTML in the view.

        Activity

        Hide
        justi9 Justin Ross added a comment -
        Show
        justi9 Justin Ross added a comment - Released in Qpid 0.24, http://qpid.apache.org/releases/qpid-0.24/index.html
        Hide
        jira-bot ASF subversion and git services added a comment -

        Commit 1513480 from Keith Wall in branch 'qpid/branches/0.24'
        [ https://svn.apache.org/r1513480 ]

        QPID-5036: View Message dialog fails to display persistance and expiration info

        svn merge -c 1510429 https://svn.apache.org/repos/asf/qpid/trunk/qpid

        Show
        jira-bot ASF subversion and git services added a comment - Commit 1513480 from Keith Wall in branch 'qpid/branches/0.24' [ https://svn.apache.org/r1513480 ] QPID-5036 : View Message dialog fails to display persistance and expiration info svn merge -c 1510429 https://svn.apache.org/repos/asf/qpid/trunk/qpid
        Hide
        justi9 Justin Ross added a comment -

        Reviewed by Robbie. Approved for 0.24.

        Show
        justi9 Justin Ross added a comment - Reviewed by Robbie. Approved for 0.24.
        Hide
        gemmellr Robbie Gemmell added a comment -

        Looks good to me, very minimal change which corrects the display of erroneous information about messages, I agree we should request this for inclusion in 0.24.

        Show
        gemmellr Robbie Gemmell added a comment - Looks good to me, very minimal change which corrects the display of erroneous information about messages, I agree we should request this for inclusion in 0.24.
        Hide
        k-wall Keith Wall added a comment -

        Hi Robbie, can you review this commit? If okay, I will request it be merged to 0.22.

        Show
        k-wall Keith Wall added a comment - Hi Robbie, can you review this commit? If okay, I will request it be merged to 0.22.
        Hide
        jira-bot ASF subversion and git services added a comment -

        Commit 1510429 from Keith Wall in branch 'qpid/trunk'
        [ https://svn.apache.org/r1510429 ]

        QPID-5036: View Message dialogue can omit or display stale field values.

        • Fixed mismatched id between json and html (message-expiration vs message-expirationTime).
        • Fixed display of stale values (values from previously viewed message would appear).
        • Fixed display of fields with the boolean value false.
        • MessageServlet changed so that JSON fields expirationTime and timestamp are included if they have non-zero values.
        • MessageServlet fails to set content type when producing JSON for single message. This caused a "not well-formed" error in Firefox Console.
        Show
        jira-bot ASF subversion and git services added a comment - Commit 1510429 from Keith Wall in branch 'qpid/trunk' [ https://svn.apache.org/r1510429 ] QPID-5036 : View Message dialogue can omit or display stale field values. Fixed mismatched id between json and html (message-expiration vs message-expirationTime). Fixed display of stale values (values from previously viewed message would appear). Fixed display of fields with the boolean value false. MessageServlet changed so that JSON fields expirationTime and timestamp are included if they have non-zero values. MessageServlet fails to set content type when producing JSON for single message. This caused a "not well-formed" error in Firefox Console.
        Hide
        k-wall Keith Wall added a comment -

        The issues are:

        1. mismatched id between json and html (message-expiration vs message-expirationTime).
        2. display of 'stale' values - that is, if I view a message with a message id, then view a message without, I see the message id from the previous message. This is caused by a scoping problem (the algorithm intends that populatedFields is shared state). Also clicking 'x' should clear the state.
        3. the algorithm fails to render boolean false values - this means non persistent messages show empty value for field (or the stale value from the previously viewed message)
        Show
        k-wall Keith Wall added a comment - The issues are: mismatched id between json and html (message-expiration vs message-expirationTime). display of 'stale' values - that is, if I view a message with a message id, then view a message without, I see the message id from the previous message. This is caused by a scoping problem (the algorithm intends that populatedFields is shared state). Also clicking 'x' should clear the state. the algorithm fails to render boolean false values - this means non persistent messages show empty value for field (or the stale value from the previously viewed message)
        Hide
        k-wall Keith Wall added a comment -

        Users may workaround this issue by using the JMX Management interface.

        Show
        k-wall Keith Wall added a comment - Users may workaround this issue by using the JMX Management interface.

          People

          • Assignee:
            gemmellr Robbie Gemmell
            Reporter:
            k-wall Keith Wall
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development