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. |