Page History
...
Error dumps are written, when the service throws an exception that is not caught. Each single error is dumped into a separate file. On tab Dump, the Bridge displays a list of all accumulated error dump files, latest first.
By setting flag Dump Context on Error in the preferences section of the xUML Service tab, you can define whether error dumps are written at all. See Preferences of an xUML Service for more information on how to set this flag.
| Note | ||
|---|---|---|
| ||
No error dump files will be created if If you are tracing the service synchronously or asynchronously with the Analyzer, no error dump files will be created. In this case, all tracing information will be picked up by the Analyzer (see Missing Tracing Information). |
Click on a filename in the list to view the content.
...
To download an error dump file, click the corresponding Download button. Once downloaded, an error dump file can be imported into the E2E Analyzer for further analysis of the error.
...
Reading an xUML Service Dump
Setting the Bridge log level of an xUML service to Debug (see Preferences of an xUML Service), the full communication stream when using the URL or SOAP adapter is written to the bridgeserver log. This is especially helpful when debugging FTP problems. If the transferred data size exceeds 8192 bytes, the stream is cut. This would also be reported in the log.
| Note | ||
|---|---|---|
| ||
Use Bridge log level Debug with care and only when investigating problems. As all information has to be logged, it may result in significant loss of performance with increasing complexity of the deployed xUML service. |
The following description explains how to generate and interpret the trace dump.
The trace dump will only be generated, if no trace request is sent via the E2E Analyzer (trace level in the test case properties set to None) and if the xUML service is running with disabled Trace (see xUML service details on the xUML Service tab).
If an error occurred, the generated error file will be indicated specified in the error message displayed in the xUML service log:
...
Overview
Content Tools