Suppose you have delivery notification set up on a logical orchestration port (along with a catch block for DeliveryFailureExceptions).
Gotchya 1: If that port is bound to a send port that executes the flat file assembler, and you send improper xml to the assembler, you’ll get a warning in the event log along the lines of:
The adapter "blah" raised an error message. Details "Cannot find definition for the input: foo”
But you won’t get a DeliveryFailureException (or any other, for that matter.) Nor will the orchestration progress past that point.
Workaround: Consider putting an xml validator as the first step in the pipeline (the flat file assembler will come next.) That will cause an exception to be raised that you can catch in your orchestration…
Gotchya 2: If the message heading for a send port is terminated within the admin console for some reason, you will never get a DeliveryFailureException, nor will your orchestration progress past that point.
Workaround: No idea on this one. Leave comment if you do…