Now it is the task to delete such a cycling message in a productive system by using the jmx-console.
The id of the message in the form ID:3dc5ec5f-4999-11e0-88ac-0015c55ff56f in known as it is logged by log4j, the operation listScheduledMessagesAsJSON of the jmx-console allows to retrieve the messageID.
But invoking the operation removeMessage on the jmx-console with the numeric messageID does not delete the message.
Several syntacticlly correct message filters based on the properties shown by istScheduledMessagesAsJSON have been tried for the operation removeMessages as well, without success.
is called with an empty filter, then the message is deleted. But this requires to stop all the possible producers that could send to that queue. This is not an ideal solution for a productive system.
Question: What is the best way to remove a scheduled message that is cycling in a loop caused by HORNETQ-495 / JBAS-7950 via the jms-console?
With best regards,
Did you find any solution to this issue?