[jboss-jira] [JBoss JIRA] (AS7-5902) HornetQ does not delete message from queue when the message is rolled back and the DLQ is not present
[
https://issues.jboss.org/browse/AS7-5902?page=com.atlassian.jira.plugin.s...
]
Ravi Bhardwaj commented on AS7-5902:
------------------------------------
I was able to achieve the expected behaviour by making the following changes in the class
"org.hornetq.core.server.impl.QueueImpl"
if (bindingList.getBindings().isEmpty())
{
QueueImpl.log.warn("Message " + ref + " has exceeded max
delivery attempts. No bindings for Dead Letter Address " + deadLetterAddress +
" so dropping it");
acknowledge(ref); // Added this acknowledge method
}
HornetQ does not delete message from queue when the message is rolled
back and the DLQ is not present
-----------------------------------------------------------------------------------------------------
Key: AS7-5902
URL: https://issues.jboss.org/browse/AS7-5902
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Ravi Bhardwaj
Assignee: Jeff Mesnil
Attachments: Bug_Testcase.zip
When a message is rolled back and the DLQ binding configured for queue is missing, the
server throws the following warning message saying that it is dropping the message,
however we can still see the message count and In Delivery count as :
WARN [org.hornetq.core.server.impl.QueueImpl] (Thread-3
(HornetQ-server-HornetQServerImpl::serverUUID=c7787105-2983-11e2-94d2-611405d536ca-619601171))
Message Reference[143]:RELIABLE:ServerMessage[messageID=143,priority=4,
bodySize=178,expiration=0, durable=true,
address=jms.queue.TestQ2,properties=TypedProperties[null]]@1575145817 has exceeded max
delivery attempts. No bindings for Dead Letter Address jms.queue.DLQ123 so dropping it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira