Handling/logging message related errors with messagebroker

ATTX-project / provenance-service

ATTX Provenance service for exposing provenance related information.

1 stars 1 forks source link

Handling/logging message related errors with messagebroker #21

Closed jkesanie closed 7 years ago

jkesanie commented 7 years ago

Description

Current implementation leaves the invalid messages to the queue by not acknowledging them and that causes weird errors and would require manual purging of the messages.

Possible solutions:

Error queues
acknowledge and raise error
can validation be implemented in the broker?
how are the messages in the error queue processed?
routing based implementation (Camel?)

DoD

Better error handling for services

Testing

Integration testing

blankdots commented 7 years ago

https://stackoverflow.com/questions/28604332/rabbitmq-ack-or-nack-leaving-messages-on-the-queue
https://www.cloudamqp.com/blog/2015-09-03-part4-rabbitmq-for-beginners-exchanges-routing-keys-bindings.html
https://www.rabbitmq.com/tutorials/tutorial-four-python.html

blankdots commented 7 years ago

The basic.ack or basic.reject should come after the processing of the message. The message should be rejected, error logged and if there is an RPC style of communication a reply message sent back.