|
| Hi,
I have an orchestration that calls a webservice using the SOAP adapter.
We ran into a case where the message that was created in the
orchestration was invalid for the webservice WSDL (there was an enum
field that had an invalid value). The SOAP adapter fails but there are
no errors returned back to the orchestration. The eventlog has a
Biztalk error "The Messaging Engine encountered an error while
suspending one or more messages."
It is a request-response type scenario, and the orchestration just sits
on the receive shape forever after the SOAP adapter fails. No
exceptions are thrown, and we tried setting Delivery Notification as
well, but no ACK/NACK is ever returned. In HAT, the message is not
suspended but shows up as "Delivered, not consumed". Setting the retry
interval on the SOAP adapter doesn't cause any retries either - it
appears as if the adapter has given up and exited. I could be wrong,
but I am guessing that since biztalk fails while trying to suspend the
message, no ACK/NACK or exception is ever generated. We also have the
SOAP.ClientConnectionTimeout property set, but I'm guessing that it is
failing before actually beginning the send (we don't see anything in
the IIS logs on the webservice machine), so the ConnectionTimeout is
never starting... just my theories, don't really know.
Has anyone run into this situation or know if there are any known bugs
with the SOAP adapter? Any suggestions on what to do?
Thanks,
Amol
|
|