[
https://issues.apache.org/jira/browse/ARTEMIS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709416#comment-17709416
]
ASF subversion and git services commented on ARTEMIS-4233:
----------------------------------------------------------
Commit 6d3dbc438389222ccaadba70ae8640b1fb0309da in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6d3dbc4383 ]
ARTEMIS-4233 Large Message Issues After Failed Clients
- interrupted message breaking reference counting
After the server writing to the client is interrupted in AMQP, the reference
counting was broken what would require the server restarted
in order to cleanup the files of any interrupted sends.
- Removed consumer during large message delivery damaging large messages
If the consumer failed to deliver messages for any reason, the message on the
queue would be duplicated. what would wipe out the body of the message
and other journal errors would happen because of this.
extra debug capabilities added into RefCountMessage as part of ARTEMIS-4206 in
order to identify these issues
> QueueImpl::NPE on holder.iter == null
> -------------------------------------
>
> Key: ARTEMIS-4233
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4233
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Priority: Major
>
> I had an user reporting the following NPE on a test:
> java.lang.NullPointerException: Cannot invoke
> “org.apache.activemq.artemis.utils.collections.LinkedListIterator.repeat()”
> because “holder.iter” is null
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:3176)
> ~[artemis-server-2.29.0-SNAPSHOT.jar:2.29.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:4331)
> ~[artemis-server-2.29.0-SNAPSHOT.jar:2.29.0-SNAPSHOT]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:57)
> ~[artemis-commons-2.29.0-SNAPSHOT.jar:?]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:32)
> ~[artemis-commons-2.29.0-SNAPSHOT.jar:?]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:68)
> ~[artemis-commons-2.29.0-SNAPSHOT.jar:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> I am adding final variables so it's validated in compile time instead to
> avoid this particular issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
