How to catch exception when remote webservice server down?

Home Page Forums BizTalk 2004 – BizTalk 2010 How to catch exception when remote webservice server down?

Viewing 1 reply thread
  • Author
    Posts
    • #14089

      Have you tried casting your system.exception into a Soap Exception and getting your inner exception? I’m guess it’s probably there.
      I thought you could catch Delivery Exceptions on WS ports But I’ve never tied. Might want to double check the help guide on Delivery Notification – it might put some light on this.

    • #14090

      You should be able to catch a SoapException. Do note that the send port settings will affect *when* the exception is actually thown.

      I wrote a bit about this here:
      http://www.winterdom.com/weblog/2005/03/30/HandlingErrorsInOrchestrationsFromInvokedWebServices.aspx

      • #14091

        Hi, All

        The issue i am facing is how to catch or handle the problem when remote web service is down.

        My orchestration will send a request to a web service and receive the response. So the web port is request-receive type. Some people mention that request-receive type, cannot catch DeliveryFailureexception, instead of that, have to catch General Exception only. It is workable to catch general exception.

        So I can catch General Exception. How ever within the scope, there are some other file IO events. Those may raise exception also.

        So other than General Exception, I also catch System.Exception behind the general exception.

        However, I found that if the System.exception exists, The web service failure would catch directly by System.Exception instead of General Exception. The ex.message is \”An error occurred while processing the message, refer to the details section for more information\”.

        Anyone have experience to work around with problem.

        Thanks

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.