[ARTEMIS-4133] Message with null property value unable to be consumed via STOMP

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.27.1
• Fix Version/s: 2.28.0
• External issue URL: https://lists.apache.org/thread/12358ypq369njlcqxvschfh8klgdmtxd
• Assignee: Justin Bertram
• Reporter: Justin Bertram
• Created: 17/Jan/23 15:17
• Updated: 14/Feb/23 10:26
• Resolved: 17/Jan/23 18:18

Description

Reproduction steps:

• Bring up an ActiveMQ Artemis 2.27.0 broker, with a queue (anycast in our case)
• Use JMS to send a text-message from Java code, with a JMS property (header) with key equal to a non-empty string and with value (string property) set to NULL. The message is added to the queue.
• Use STOMP (we use stomp.py) to subscribe to the queue with the text-message on it. The message will not be received, apparently because of the null value in the JMS property (header). At the default logging level no issue is reported by ActiveMQ Artemis. Also via the STOMP protocol no error is received. Any messages that are added to the queue which do not have headers with a NULL value are received properly via STOMP.

Note: we haven't tested what happens if the key is NULL and the value is not

Workaround:

• Use a value unequal to NULL for the value of each JMS property (header)

Issue Links

• links to: GitHub Pull Request #4335