Hi, I think we've discovered a bug in ActiveMQ Artemis.
We can work around the bug very easily, so frankly we're not interested in an account or ownership of this issue. If someone can reproduce the issue, perhaps it could be added to JIRA? 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) Kind regards, Koen ________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. Ministerie van Justitie en Veiligheid This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. Ministry of Justice and Security
