| Karagu 2004-11-25, 7:46 am |
| Hi!
I have a receive pipeline in which I implement a custom pipeline component
(CPC) that converts excel files to flat text files.
As long as the incoming files are correct according to the xsd-schema the
pipeline validates them with, everything works just fine. But if I drop a
file that in some way is incorrect (for example, a file that contains one
column too many), I get the following behaviour:
Instead of removing the incorrect file from the receive location-catalog and
just suspending the message, BTS keeps the file in the receive
location-catalog, and logs the following two errors in the application log
(in addition to the other two errors generated by the validation failure
itself):
The Messaging Engine encountered an error publishing a batch of "1" messages
to the Message Box database for the transport adapter "FILE". Please refer to
Health and Activity Tracking tool for more detailed information on this
failure and check the endpoint bindings are correctly configured.
and
The Messaging Engine encountered an error committing a transport adapters
batch containing the following work items: FILE messages to be published, 0
request-response messages to be published, 0 messages to be suspended, 1
messages to be deleted from a host queue, 0 messages to be resubmitted for
later transmission, 0 messages to be moved to their backup transport. Please
refer to Health and Activity Tracking tool for more detailed information on
this failure.
The only entry in HAT is the one telling that the pipeline terminated due to
the validation failure (which is exactly the same as if I submit an incorrect
file through a pipeline in which I DON'T implement my CPC).
This behaviour is then repeated once every minute, until I manually delete
the file from the receive location-catalog.
I suspect this problem has something to do with the property promotion
needed to be able to send the message to the message box database, but I
can't find any solution... And if the property promotions really are the
problem, how come everything works fine if the incommÃ_ng message is
correct...?
Any help is reeeeeeeally appreciated!!
Thanks in advanced!
|