About service policy

Replies to This Discussion

Permalink Reply by Joe Klug on November 5, 2015 at 8:44am

Yeah, you're right - there isn't any documentation on Service Policies.  I'll have to answer your questions directly:

#2 - I usually call a service fault a managed exception returned by the called Web service.  What that typically means is that the Web Service accepted the call, decided that something was wrong with the request (for example, a missing element or invalid value for an element, and constructed an error, the "fault", that is returned to the client.  The http status code for a service fault would be 200.  Non-service faults would be a 500 response or something like an endpoint not found exception.  I can't give an actual example of a service fault because it's up to the Web service developer to define them.

#3 - No.  None of the settings listed are applied to client connectors.  They are only applied to service connectors.  The only setting applied to a client connector is an expiration time stamp that is calculated from the MSMQ retry expiration value.

• ▶ Reply