-
Bug
-
Resolution: Done
-
Major
-
7.0.1.CR2
-
Documentation (Ref Guide, User Guide, etc.)
-
-
-
-
-
-
Scenario description
Server is started and queue is deployed. Address setting is configured to recognize queue as a last value queue and thresholds are lowered to start paging soon. Producer sends 300 messages with 300 different _AMQ_LVQ_NAME configured to different values (server is paging). Then producer sends message with _AMQ_LVQ_NAME property which has already been used. Total number of send messages is 301. Receiver receives messages from last value queue
Expectation
Consumer should receive only last send message for each _AMQ_LVQ_NAME property, it means 300 messages total, every message should contain different value of _AMQ_LVQ_NAME property and only the most recent message for each _AMQ_LVQ_NAME should be kept.
Actual results
Consumer receives 301 messages. All send messages are delivered, including messages with same value of _AMQ_LVQ_NAME property. This happens only when server is paging. It works when server is not paging.
- is cloned by
-
JBEAP-8517 Last value queue doesn`t work correctly with paging
- Closed
- relates to
-
JBEAP-5127 Order of messages with messsage grouping breaks when paging is used
- Closed