I am using a Wildfly 8.1 and have the following scenario.
I have a queue defined which is a Last Value Queue, now when the data is consumed by the consumer from the queue , whenever consumer rollbacks the transaction ideally my data should go back in the queue and come back for processing after some time, but what is happening is that it is going in the DLQ since it is detecting it as a duplicate and routing the message to DLQ, is that a behavior or a bug.
For example I have the following queue defined.
And following is the setting which marks it as Last Value Queue.
Now when I send the message to queue I set the HQ_LVQ property. Now when my consumer is consuming , because of my application requirements I am rolling back the transaction which sends a signal to the queue to redeliver the message after 5 minute , this i have done using the configuration parameter
But somehow the messages are moving to DLQ may be because it is detected as duplicate by the LAST VALUE QUEUE.
Can Someone help me out on this.
HornetQ ships with a last-value-queue example. Could you modify that example to reproduce the issue you're seeing and zip/attach the modified example here?