You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we are creating a middleware and also a router plugin that allows reprocessing of messages that failed and went through a poison/dead letter topic.
In order to be able to reprocess the messages without needing to republish them in the same topic,
that other applications can be listening, the router plugin should be able to access the handlers.
We can create a router plugin that could expose the reprocess functionality via an HTTP endpoint, for example.
The text was updated successfully, but these errors were encountered:
Exposed the registered router handlers to be used by a router plugin in order to allow use cases such as message reprocessing describe in issue ThreeDotsLabs#288
Exposed the registered router handlers to be used by a router plugin in order to allow use cases such as message reprocessing described in issue ThreeDotsLabs#288
Exposed the registered router handlers to be used by a router plugin in order to allow use cases such as message reprocessing described in issue #288
Co-authored-by: Davi Henrique <davi_henrique@sicredi.com.br>
Hi, we are creating a middleware and also a router plugin that allows reprocessing of messages that failed and went through a poison/dead letter topic.
In order to be able to reprocess the messages without needing to republish them in the same topic,
that other applications can be listening, the router plugin should be able to access the handlers.
We can create a router plugin that could expose the reprocess functionality via an HTTP endpoint, for example.
The text was updated successfully, but these errors were encountered: