NonStop SOAP User's Manual

NonStop SOAP Features and Functions
NonStop SOAP User’s Manual—520501-012
4-71
Mapping Between Faults, Error Logs, and Trace
Records
1. Look at the detailString element of the fault message. (If you are writing a client
and wish for users to report faults as described here, you must externalize the ts
attribute and the text message in this element.)
2. Examine the error log. Find the record that matches the ts attribute and text of the
fault message, and note the process name. Skip this step if you ran the SOAP
server from the command line.
3. Examine the trace file that has the same process name appended to the base
trace filename. For example, if the configuration specifies a base trace filename of
soapcgi.trc and the error log entry contains the process name CM01, find the
trace file named soapcgi.trc.CM01. Find the record that matches the ts
attribute and text of the fault message. Analyze the trace records before and after
the matching record to discover the processing context in which the fault occurred.
Example of Correlating a Fault, a Log Entry, and a Trace
Record
This example demonstrates the procedure just described.
Fault Message
The client receives this fault message. The detail string contains the ts attribute and
text describing the error.
Example 4-41. Mapping Between Fault Message, Error Log, and Trace Entry
(Fault Message)
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Error unmarshalling request</faultstring>
<detail>
<detailCode>-202</detailCode>
<detailString ts="2001/08/21 16:06:22">Unmarshal Error: node: alias is
either NULL or not present. Incorrect sequence of nodes in request. Input
request XML does not conform to DTD
</detailString>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>