[
https://issues.apache.org/jira/browse/ARTEMIS-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699806#comment-17699806
]
Artyom Tarasenko commented on ARTEMIS-4095:
-------------------------------------------
I don't know if the producer/checker script has any use to you because it's
trivial:
{code:java}
$ cat torture-artemis.bash
#/bin/bash
for i in {1..32}; do
echo "Iteration ${i}"
jmeter -n -t JMSPublisherDev-test-3000-localhost.jmx
tail -1 /opt/artemis-broker/log/artemis.log |grep --color=always
'AMQ222038: Starting paging'
if [ $? -ne 0 ]; then
echo "Not enough pressure to start paging"
exit 1
fi
sleep 230
tail -1 /opt/artemis-broker/log/artemis.log | GREP_COLORS='ms=01;32'
grep --color=always 'AMQ224108: Stopped paging'
if [ $? -ne 0 ]; then
echo "either slept too less, or we have hit it"
exit 2
fi
done{code}
We use JMeter to flood the same message (the message itself doesn't seem to
matter), ensure that artemis starts paging, then wait till the JBoss/servicemix
consumer consumes messages till artemis gets out of paging mode and then we do
it again.
> 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, 2.27.0, 2.27.1
> Environment: Artemis, deployed through the official docker image in
> version {{2.26.0}} in an OpenShift cluster
> Reporter: Marco Bungart
> Priority: Major
> Attachments: artemis-Xmx1G.png, artemis-Xmx2G.png, 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)
