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.

...

The dump file shows the context of the error: e.g. error description and call stack, marked in the picture above. You can load the dump file and import it into the E2E Analyzer or E2E Interactive Debugger Builder Image Addedto do more investigation on the error.

...

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 specified in the error message displayed in the xUML service log (see xUML Service Dump):

[2010-09-22 07:46:18 +0200][Error][Internal][FUASM][3][Division by zero - Error Trace: logs/error/error-2014-06-03_11-32-14_UTC-0.xml - Callstack: calculate > urn:Services.Calculation.Ports.CalculationPortType.calculate > Division > Division > Division(1)]

The error file is located in the directory of the xUML service (location: <your bridge data directory>\<name of the service>\logs\error). It contains the call stack and the corresponding XML trace of the activity diagram where the error occurred.

...