RE: Unexpected message order after JMSContext.recover()

2023-07-21 Thread Moritz Heine
Hello, whoever stumbles upon that issue: I figured out that I can achieve the needed behavior by using the the session mode *SESSION_TRANSACTED*. So instead of using *acknowledge()* and *recover()* I'll use *commit()* and *rollback()*. This seems to fix the order when redelivering messages as

Unexpected message order after JMSContext.recover()

2023-05-26 Thread Moritz Heine
Hello, I've observed a somewhat unexpected behavior of message delivery after a recover with the following setup: - Artemis broker (tested with 2.24.0 and 3.0.0) - JMSConsumer (shared durable) *C* with *ActiveMQJMSConstants.INDIVIDUAL_ACKNOWLEDGE* - JMSProducer (shared durable) *P*