allow rollback to retry three times - if inside the flow I get an error I know I can handle, handle it and raise an alert.
if i handle the error within the flow then the transaction would be successful and the DB changes will not be rolled back.
if i have an err flow to handle these messages, then if something blows up in that err flow then it would go to the DEAD.LETTER.QUEUE which as you said is not a good thing
so heres what i plan to do:
i create an alert(warning so that a ticket is not generated) and include the MsgId of the message that caused the error within the warning and then throw and exception so that the changes are rolled back and the message goes to the err queue but we have a way of correlating the message and the alert infrmation
but all this again goes back to the visibility of the err queue, i think we should push back on them saying the support guys should have access to the production queues!!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum