Bug 901177 (JBPAPP6-857)

Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000BdP1V&sfdc.override=1
Steps to Reproduce:     * Create a queue and set any binding as DLQ address. Make sure that the DLQ binding does not exists.
    * Send a message to the queue.
    * From the standalone consumer, create a transacted QueueSession and rollback the transaction.
    * Expected behaviour is, when the delivery attempts are reached, the message should have been deleted from the queue and the "Message count" and "In Delivery" count should be 0.


Workaround: Workaround Exists
Workaround Description: Make sure the DLQ binding is present so that the message could be moved to the DLQ instead of deleting it.
project_key: JBPAPP6

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