Release 10.1A: OpenEdge Development:
Web Services

> ## Scenario 3: Web service deployed but AppServer not running

> In this scenario, a Web service is deployed, but its AppServer is not running. At this point:

> 1. The client sends the following connection request:

>     Connect_Orderinfo("", "", ")

> 2. The WSA:

> 1. Gets the request.
> 2. Determines that the AppServer is not available.
> 3. Records the following in its log:

>     [02/12/11@16:17:27.349-0500] P-000120 T-Thread-11 2 OrderInfo
>     4GL-Provider (reqid:8) Error in SOAP request execution: Connect
>     Failure: Application Service asbroker1 Unknown at NameServer
>     at Host servicehost Port 5162. (8234) (10926)

> 4. Sends a SOAP message with a SOAP fault back to the client. The message is as follows:

>     <?xml version="1.0" encoding="UTF-8" ?>
>     <soap:Envelope  namespaces defined here…>
>       <soap:Body>
>         <soap:Fault>
>           <faultcode>SOAP-ENV:Server</faultcode>
>           <faultstring>An error was detected … request. (10893)
>           </faultstring>
>           <detail>
>             <ns1:FaultDetail
>               soap:encodingStyle=“http://schemas.xmlsoap.org/…/”
>               xmlns:ns1="http://servicehost:8080/wsa/wsa1">
>               <errorMessage xsi:type=“xsd:string">Error in SOAP request
>                 execution: Connect Failure: Application Service
>                 asbroker1 Unknown at NameServer at Host servicehost
>                 Port 5162. (8234) (10926)
>               </errorMessage>
>               <requestID xsi:type=“xsd:string">2e62cab6b81150d5:
>                 -87f76e:f20f57227d:-8000#8 </requestID>
>             </ns1:FaultDetail>
>           </detail>
>         </soap:Fault>
>       </soap:Body>
>     </soap:Envelope>

> 3. The interface translates the SOAP fault into a SOAP exception.

> 4. The client catches the SOAP exception.

> 5. The client displays the this error message (assuming the client application has a user interface):

> Note: All .NET client applications should always catch SOAP faults and handle them. If not, the .NET Framework’s default exception handler displays the SOAP fault general error information. This might well hide and cause the loss of the more useful error detail information in the SOAP fault. For client applications without a user interface, all error information must be written to an application log file to ensure it is not lost.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095