Hi @Naga, message ordering sounds simple but the conversation always ends up being involved.
Solace by default enforces message ordering, with the unit of order being reception time at the broker. You should use a queue to ensure that ordering is maintained even if the consumer is offline.
Things get more complicated when we start to think about consumer failures. What if the consumer gets OD1 and it causes the consumer to crash? Well, you have some knobs to twiddle. If OD1 must be before OD2 even at the expense of system failure, leave the queue defaults as they are. If, however, you’d like to set a maximum number of re-tries before the broker considers OD1 to be “poisonous” and optionally discard or move it to a dead message queue, then change the “Maximum Redelivery Count” setting on the queue.