[
https://issues.apache.org/jira/browse/ARTEMIS-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637875#comment-17637875
]
Artyom Tarasenko edited comment on ARTEMIS-4095 at 11/24/22 4:24 PM:
---------------------------------------------------------------------
Manually calling retryMessages() on the stuck channel fixes consuming without
restarts of Artemis or consumer. So, at least we have a workaround now.
Since retryMessages() seems to do with DLQ, we redone tests with
<max-delivery-attempts>-1</max-delivery-attempts> and with
jms.redeliveryPolicy.maximumRedeliveries=-1 on the client side, but it made no
difference.
Also calling retryMessages() causes thousands
WARN AMQ222188: Unable to find target queue for node null
warnings in the log, one warning per message in the stuck queue.
was (Author: JIRAUSER298414):
Manually calling retryMessages() on the stuck channel fixes consuming without
restarts of Artemis or consumer. So, at least we have a workaround now.
Since retryMessages() seems to do with DLQ, we redone tests with
<max-delivery-attempts>-1</max-delivery-attempts> and with
jms.redeliveryPolicy.maximumRedeliveries=-1 on the client side, but it made no
difference.
Also calling retryMessages() causes thousands
WARN AMQ222188: Unable to find target queue for node null
warnings in the log, one warning per message in the stuck queue.
Analyzing heap dump, the stuck queue is the only
{color:#242424}org.apache.activemq.artemis.core.server.impl.QueueImpl where
qi.deliveriesInTransit.control.state=1{color}
> OpenWire clients are unable to consume from mutlicast queue after 2nd paging
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-4095
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4095
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.26.0
> Environment: Artemis, deployed through the official docker image in
> version {{2.26.0}} in an OpenShift cluster
> Reporter: Marco Bungart
> Priority: Major
> Attachments: graph1.png, graph2.png
>
>
> I observed that after artemis went into paging for the 2nd time, OpenWire
> clients were not able to read messages from their corresponding addresses.
> Restarting the applications connected as clients does not fix the issue.
> Restarting artemis, however, does fix the issue.
> Both images attached show the messages of two queues.
> - The upper (orange) line in the 1st graph shows count of messages in a queue
> to which core clients are connected.
> - The lower (blue) line in the 1stg raph shows count of messages in a queue
> to which OpenWire clients are connected.
> - in the 2nd graph, the upper (violet) line shows count of messages in a
> queue to which core clients are connected.
> - in the 2nd graph, the lower (green) line shows count of messages in a queue
> to which OpenWire clients are connected.
> I have a heap dump that we could share, showing the accumulated objects. the
> dump is about 90 MB in size If this would be helpful to have, please let me
> know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
