Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use dead letter queues instead of sending to the topic #99

Open
arsulegai opened this issue Jul 14, 2023 · 0 comments
Open

Use dead letter queues instead of sending to the topic #99

arsulegai opened this issue Jul 14, 2023 · 0 comments

Comments

@arsulegai
Copy link
Member

The transaction are processed via the input topic. These transactions are sent to Fabric network for processing. In case of an error, it is further analyzed to see if it is due to the recoverable errors or if it is due to an error reported by Fabric. If the reported error is because of blockchain's operation such as the case of no consensus, these are reported back to the user through the output topic.

The concern however is that the output topic is specifically subscribed to report either the block event or the chaincode event. The error event type is a surprise entry in the topic. Typical place to report such errors is through the dead letter queue.

eventPublishServiceImpl.publishTransactionFailureEvent(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant