Oracle GlassFish Message Queue 4.4.2 Developer's Guide for Java Clients

Predefined Fault Codes

The SOAP specification lists four predefined faultcode values. The namespace identifier for these is

Table 5–3 SOAP Faultcode Values

Faultcode Name 



The processing party found an invalid namespace for the SOAP envelope element; that is, the namespace of the SOAP envelope element was not .


An immediate child element of the SOAP Header element was either not understood or not appropriately processed by the recipient. This element’s mustUnderstand attribute was set to 1 (true).


The message was incorrectly formed or did not contain the appropriate information. For example, the message did not have the proper authentication or payment information. The client should interpret this code to mean that the message must be changed before it is sent again. 

If this is the code returned, the SOAPFault object should probably include a detailEntry object that provides additional information about the malformed message.


The message could not be processed for reasons that are not connected with its content. For example, one of the message handlers could not communicate with another message handler that was upstream and did not respond. Or, the database that the server needed to access is down. The client should interpret this error to mean that the transmission could succeed at a later point in time. 

These standard fault codes represent classes of faults. You can extend these by appending a period to the code and adding an additional name. For example, you could define a Server.OutOfMemory code, a Server.Down code, and so forth.