smallrye-reactive-messaging icon indicating copy to clipboard operation
smallrye-reactive-messaging copied to clipboard

AMQP Multiple failure management strategies

Open ramiayoub-priv opened this issue 1 year ago • 0 comments

Is it possible to have different failure management strategies for the same connector?

An example of why this would be useful in a kube environment:

  • If the message processing fails due to an unexpected error, such as temporary loss of db connection or some other temporary error, reprocessing should be attempted. In this case the fail strategy could be useful as it stops subsequent processing and the pod will restart
  • If the message fails due to validation error, it should be rejected but processing should continue.

Is there any workaround or better way to handle these scenarios?

ramiayoub-priv avatar Mar 06 '23 14:03 ramiayoub-priv