You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2023/01/18 20:07:00 UTC

[jira] [Resolved] (ARTEMIS-3819) stack traces in console output on browse queue due to missing validatedUser value

     [ https://issues.apache.org/jira/browse/ARTEMIS-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-3819.
-------------------------------------
    Fix Version/s: 2.28.0
       Resolution: Fixed

> stack traces in console output on browse queue due to missing validatedUser value
> ---------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3819
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3819
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 2.22.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>             Fix For: 2.28.0
>
>         Attachments: image-2022-05-07-23-14-52-440.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When browsing the messages of a queue, stack traces are produced in the brower console.
>  !image-2022-05-07-23-14-52-440.png!
> This happens when an individual message is inspected.
> The error is caused by field {{validatedUser}} which (at that time) does not have a value, it is {{undefined}}. The JS code crashes on this in the corresponding {{templateFn}} function.
> The error is repeated as there are multiple records and the table is refreshed every few seconds.
> The protocol that was used is AMQP.
> I'm quite sure that this did not happen with versions up to 2.20.0.
> I did not have the opportunity to test this with 2.21.0 as I skipped that version.
> ===
> update:
> reproducible by sending a small message using the web-console to address DLQ and browse the messages for the queue below that address.
> a message sent in this way does not have a validated user, nor does it have an original queue, thus triggering two problems conditions.
> a simple PR is added.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)