It looks to me like the consumer active while messages are being sent to the queue. If that's the case then you're seeing the expected behavior because even though the consumer isn't actually calling receive() or whatever the broker is still dispatching messages to it in the background when they arrive in the queue. That means those messages will be "in delivery" from the broker's point of view and cannot be replaced by the last-value semantics.
Justin On Fri, Dec 13, 2019 at 3:13 PM ldebello <[email protected]> wrote: > Hi, > > This is some kind of related to my previous question, because I am checking > different options but getting some weird behaviors. > > We have an Artemis Broker 2.9.0 (Single Node - No Cluster) and doing the > following test > > Queue: State (Last Value Queue) > > Producer Send Message: Message(LVQ_ID="Some", Content=1, Queue=State) > Consumer Read Message: Message(LVQ_ID="Some", Content=1, Queue=State) > Consumer Wait 30 seconds > > In the meanwhile: > Producer Send Message: Message(LVQ_ID="Some", Content=2, Queue=State) > Producer Send Message: Message(LVQ_ID="Some", Content=3, Queue=State) > > 30 seconds after > Consumer Read Message: Message(LVQ_ID="Some", Content=2, Queue=State) > Consumer Read Message: Message(LVQ_ID="Some", Content=3, Queue=State) > > I was expecting consumer read Content=3 because the queue is LVQ. > > Is my understanding correct? > > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html > >
