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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.22.0
• Fix Version/s: 2.28.0
• Component/s: Web Console
• Assignee: Unassigned
• Reporter: Erwin Dondorp
• Created: 07/May/22 21:32
• Updated: 14/Feb/23 10:26
• Resolved: 18/Jan/23 20:06

Description

When browsing the messages of a queue, stack traces are produced in the brower console.

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.

Issue Links

• is caused by: ARTEMIS-3765 Display validated user in Hawtio
• links to: GitHub Pull Request #4337