Missing Stack Trace in the Response SOAP Fault Message 

Problem Description

When there is an error in the Web services processing, a SOAP fault message is returned as a response. The fault message contains a fault code and a fault string explaining shortly what the reason for the failure is, but there is not a server-side stack trace included.

 

Scenario Type:	Error analysis
NetWeaver Component:	J2EE Engine
Validity:	J2EE Engine 6.40 and higher

 

Possible Error Sources

Error Source	Analysis
Consuming J2EE Engine Web services	The SOAP fault messages returned by the server do not contain stack traces describing the method chain of the error.

Decision Roadmap

Prerequisites

Response SOAP fault messages do not contain stack traces because of security issues, it is possible for efficient attacks to be performed against the server (for example, DenialOfService).

To analyze the error, it is necessary for the severity of location com.sap.engine.services.webservices.runtime and its subtree to be set to DEBUG, in this way the stack trace will be stored in the trace file. You can change the severity level in the Visual Administrator → Log Configurator Service, under the Locations tab.

Main Tools

Visual Administrator