Solace Topic Destination Header
Hi Team - this is regarding the scenario of publisher using topic string as destination header (using topic hierarchy) and consumer using wild card (> or *) to consume required message. This is in order to facilitate filtering at event broker level.
Does the above scenario ensure guarantee message delivery when none of the consumer is online?
Example: Publisher sends below messages (there is no end point created in broker)
Msg1 Destination Header: OMS/EQ/AK/1
Msg2 Destination Header: OMS/EQ/AK/2
Msg3 Destination Header: OMS/EQ/AS
Consumer1 has 2 instances subscribing to 'OMS/EQ/>'. Consumer2 has 2 instances subscribing to 'OMS/EQ/AK/>'. Assume that both instances of Consumer2 are down.
Consumer1 receives all 3 messages. But since Consumer2 has both instances down, does Solace event broker store those 2 messages (with header OMS/EQ/AK/1 and OMS/EQ/AK/2) and deliver them to Consumer2 once it comes online?