- This topic has 2 replies, 1 voice, and was last updated 3 years, 5 months ago by
.
-
Posts
-
-
Hello
I have an orchestration deployed to a production server that sends a request on a static solicit-response port to a webservice (i.e. SOAP).The receive pipeline is a custom pipeline that does nothing except XML disassemble with an explicit schema specified. The setup was working fine till yesterday when we had an issue on the webservice. I resolved the problems on the webservice and at the same time noticed that BizTalk was reporting a number of tmie-outs on the port. To resolve the time-outs I changed the port to be ordered delivery, which seems to help. However since then I have started receiving a routing failure on some, but not all, of the messages returning from the webservice.
I’ve checked the usual things – the ports, orchestration etc. are all enlisted and started. I have restarted the host. I have also changed the port back to un-ordered delivery, but still receive routing failures. I don’t have any promoted properties on the response message (I’m not even sure how to promote properties on a webservice response).
I have two main questions:
- What could cause a routing failure on a webservice response – surely it’s a simple scenario and should “just work”?
- What methods are recommended for tracing routing errors? I have searched the web and seen how to interrogate the routing failure report, but I still don’t know what to look for. I understand the basic concept of a routing error, I can see which port is failing and I can retrieve the message that’s failing, but I’m still lost.
Please help!
Sean
PS Please tell me BizTalk 2010 is going to be easier to use and debug. I find 2006 R2 extremely frustrating.
-
Hi Sean,
Are you doing any exception handling in your orchestration when sending a request and receiving a response from the SOAP web service? I have a similar BizTalk project in production, that has a Scope shape (with properties Synchronized set to “False” and Transaction Type set to “None”) encapsulating the Logical Send and Receive shapes, and multiple Catch Exception shapes to handle four different Exception Object Types (Time Out, Soap, XLangs, System). To create a Catch Exception shape, highlight the Scope shape, right-click and choose the first option (New Exception Handler). I then use MS Enterprise Library Logging Application to output any errors to a log file, but you could do something different, like sending an email notification…
If you haven’t done so already, you should look into implementing exception handling in your orchestration to trap any errors returned from calling the web service.
Cheers,
Daniel.
-
The Prettiest by Brigit Young · 9781626729230
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.