Create a destination , queue/A : <queue name="A"> <entry name="/queue/A"/> </queue> Configure HornetQ to page persisted messages. Set PAGE for address-full-policy while keeping the page size to a lower figure : <address-settings> <address-setting match="#"> <dead-letter-address>jms.queue.DLQ</dead-letter-address> <expiry-address>jms.queue.ExpiryQueue</expiry-address> <redelivery-delay>0</redelivery-delay> <max-size-bytes>15728</max-size-bytes> <page-size-bytes>64</page-size-bytes> <message-counter-history-day-limit>10</message-counter-history-day-limit> <address-full-policy>PAGE</address-full-policy> </address-setting> </address-settings> Sent ~7000 messages each holding 204799 bytes Make sure that the messages have been paged. Please use JMX console. Invoke jmsQueueControl.removeMessages(null). This would remove in-memory messages but not the ones which were paged. There was no success during subsequent calls of the given API method.

Messages for any given queue could not be removed when the messages were paged. The HornetQ core API removed only the in-memory messages but not the paged ones when jmsQueueControl.removeMessages(null) was used. This problem has now been solved and both paged and non-paged message are successfully removed from the message queue.