When running a multi-threaded consumer for AMQP messages, the server will sometimes generate WARN-level log messages of the form:

2024-05-13 18:11:46,048 WARN  [io.netty.util.concurrent.AbstractEventExecutor] A task raised an exception. Task: org.apache.activemq.artemis.protocol.amqp.proton.AMQPLargeMessageWriter$$Lambda$643/0x00007fa4ff5153c0@33bff98e
java.lang.NullPointerException: null

The messages are produced when the client finishes consuming messages.  They are sometimes accompanied by a stack trace, but not always.

No messages are lost, so the message appears more concerning than it actually is.

Problem noticed when testing for ENTMQBR-8905, so is likely related to the AMQP handling changes there (https://issues.apache.org/jira/browse/ARTEMIS-4668).