You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christian Danner (Jira)" <ji...@apache.org> on 2022/03/10 13:29:00 UTC
[jira] [Commented] (ARTEMIS-3717) NullPointerException in AMQPMessage when browsing queue with Artemis web console
[ https://issues.apache.org/jira/browse/ARTEMIS-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504262#comment-17504262 ]
Christian Danner commented on ARTEMIS-3717:
-------------------------------------------
I also attached the patched class - it attempts to eliminate the possibility of NPE caused by toString() calls in general.
> NullPointerException in AMQPMessage when browsing queue with Artemis web console
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-3717
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3717
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.19.1
> Reporter: Christian Danner
> Priority: Major
> Attachments: AMQPMessage.java, AMQPMessage_NPE_StackTrace.txt, image-2022-03-10-14-15-14-686.png
>
>
> Attached is a stack trace of a NullPointerException that happens when browsing a dead letter queue. It seems the NPE is caused by the following code in org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage (line 874):
> {{map.put(extraPropertiesPrefix + s.toString(), JsonUtil.truncate(o.toString(), valueSizeLimit));}}
> because the property value can obviously be null. Applying a patch that calls String.valueOf(o) instead fixes the NPE and it can be seen that the problem is caused by the AMQ_ORIG_QUEUE property whose value is null:
> !image-2022-03-10-14-15-14-686.png!
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)