Bridge Server Log Levels of an xUML Service

The following Bridge server log levels can be set for each selected xUML service. The higher the log level the more information will be written to the log files. The log levels in the table below are cumulative and are ordered from the lowest to the highest log level. For each log level, also the information of the lower levels is logged.
Viewing this log is described on Logging of xUML Services.

Log Level	Description
None	No logging will be executed.
Fatal	Fatal errors are logged. The component cannot continue with normal execution. Examples: repository errors, system limitations like no more available threads or memory. These errors need the intervention of an administrator to solve the problem.
Error	Also non-fatal errors are logged. If the UML modeler catches these errors, they are not written to the log. Examples are connection errors, wrong SQL statements, applying operations to invalid values, and so forth. Errors of this category are further classified: User Errors: Exceptions explicitly thrown in the UML model. External Errors: IO exceptions, such as problems when connecting a backend, wrong input formats, and so forth. Internal Errors: Bridge operations cannot be executed, because of internal problems, e.g. unexpected NULL values, full queues, and so on.
Warning	Warnings are logged. Warnings indicate unexpected but non-critical situations that do not interrupt normal operation.
Info	General information is logged. This includes, for instance, which component is being started or stopped, loaded add-ons, licensing information, etc.
Debug	In addition to log level Info, detailed trace information is written into an error file specified in the error message. Furthermore, the full communication stream when using the URL or SOAP adapter is written to the xUML service standard log. For more details on debugging an xUML service, see xUML Service Dump. Use this log level with care and only when investigating problems. As all tracing information has to be logged, it may result in significant loss of performance with increasing complexity of the deployed xUML service.

If an error occurred, a call stack is written into the error log exposing the path to the action state where the error occurred in the model.
[2006-04-20 08:31:13 W. Europe Standard Time][Error] [Internal][FUASM][3][Division by zero - Callstack: calculate > Calculation > call_Division > Division > Divide]