Closed michielswaanen closed 4 years ago
@michielswaanen
nats-streaming clients don't support such a feature that I am aware of - @kozlovic can confirm.
It doesn't make a sense for a persistent system to have such a limit, as the intention is to process all messages if the message has some data that prevents its processing, the application likely should implement some sort of dead letter queue where the message is sent to another channel for additional processing or inspection, this, of course, means that the forwarding client has to ack the message.
Ok thanks! A dead letter queue sounds good, I'm kinda new to event based stuff. Does node-nats-streaming support dead letter queue functionality out of the box @aricart ?
Hey,
Does the node-nats-streaming library support setting a redelivering limit? Can't seem to find anything about this.