Durable LVC exchange should persist the cached message (if persistent) across RabbitMQ restarts.

[dcorbin]

1. Create a durable LVC exchange
2. Publish a persistent message to it.
3. Confirm that binding a queue to the exchanges causes that message to be delivered to the queue.
4. Restart RabbitMQ
5. Bind a queue to the exchange - notice that no message is delivered, but my expectation is that it will deliver it.

[dcorbin]

If it's helpful: https://stackoverflow.com/questions/55456797/how-can-i-get-the-lvc-exchange-in-rabbitmq-to-persist-the-cached-value-across-ra

[lukebakken]

If implemented, this probably won't take clustering into account.

[dcorbin]

For my immediate uses, thats fine.

[bharath1718]

We observed something where after a recycling the cluster nodes in a rolling fashion the queue bound to a LVC exchange did return the sequence number. Durable is set to true.
[[..]]
com.gs.futures.jetstream.messaging.services.infra.rabbitmq.LvcSequenceManagerRabbitmq - No Sequence Number received
[[..]]