Can somebody explain me how last value queue behave for messages buffered on cliend side or being under consumption. Lets say that message has long consumption time, and during it processing, message with the same _HQ_LVQ_NAME value pop into the queue. My experiments shows that it will be added as a new one. Is it valid behaviour? Is there any way to keep message unique till end of processing?
As soon as the message leaves for the client, it will leave the server's queue as handled, then the LastValueQueue will be ready to receive a new message.
If you have slow consumption.. you should use slow consumption by setting consumerWindowSize=0 on your consumer, what would avoid client caching.