Soap Adapter timeouts and other failures

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Soap Adapter timeouts and other failures

Viewing 1 reply thread
  • Author
    Posts
    • #21000

       I have a solution using a generic ‘on-ramp’ to deliver messages to Biztalk via the WSE adapter. I then have a set of SendPorts configured to use the SOAP adapter to deliver these messages to an approriate web service based based on rules defined in the filter configuration for each SOAP adapter. This all works fine.

      However, what i want to do is return a sensible response to the calling application if either

      a) An invalid message is sent (one which does not match any of the rules on the send port). I know I need to use Failed message routing but I am not sure what should handle the failed message. I tried an Orchestration with a ‘failed message’ filter on the receive shape and while this gets called, the message sent back from the Orchetration gets suspended as there are no subscribers to the message.

      b) A call to any of the web services times out. If this happens I don’t want Biztalk to retry, just return a message to the calling application. I have the retry count etc set to zero but get into the same problems as in a) above.

      I’m sure the answer is failrly straightforward – i just can’t figure it out!

      Thanks

      NigelT

       

       

       

       

    • #21677

      Hello put your orchestation in Long Runnig mode, set a timespam, and before the message be sent, put this lines.. messagename(soapclientconectiontimeout) =  number in miliseconds.

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