Mustafa Bozdemir created AMQ-8054:
-------------------------------------
Summary: mq_out If queue full, mq_out never picks up new messages
Key: AMQ-8054
URL: https://issues.apache.org/jira/browse/AMQ-8054
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.16.0, 5.15.0, 5.14.0
Reporter: Mustafa Bozdemir
Attachments: KORDOBA-981_ActiveMQ_5.16.0_TestWithPurging.docx
Hi currently we are facing severe issues for ActiveMQ:
I have verified this scenario of deleting messages in queue with below steps.
1.Set a maximum storage space in activeMq.xml config file.
2.Both ActiveMQ and mq_out is started.
3.mq_out is started and processed to put messages to queue.
4.when the maximum storage of ActiveMQ is reached, then mq_out doesn't send
messages to queue since the storage is already full.
At this point when we try to purge messages from queue, the storage space is
not released and still storage remains full. so eventually mq_out is also not
able to process other messages to queue.
On the other side, when both ActiveMQ and mq_out is running and when tried to
manually free up space by deleting kahadb folder from ActiveMQ in the path
apache-activemq-5.16.0-> data ->kahadb , then automatically the mq_out is able
to start posting remaining messages to the queue.
So we see mq_out is not having any issue here and looks like AcitveMQ purging
is not freeing up the storage space. So this has to be verified from ActiveMQ
side and see how the purging is handled.
(Attached the document with tested screenshots
[KORDOBA-981_ActiveMQ_5.16.0_TestWithPurging.docx^!https://kordobajira.fnfis.com/images/icons/link_attachment_7.gif|width=7,height=7!^|https://kordobajira.fnfis.com/secure/attachment/17290/17290_KORDOBA-981_ActiveMQ_5.16.0_TestWithPurging.docx]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
