[
https://issues.apache.org/jira/browse/ARTEMIS-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-3819:
-----------------------------------
Description:
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.
was:
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.
> 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
> Attachments: image-2022-05-07-23-14-52-440.png
>
>
> 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)
