Contents of the xUML Service Log
For running services, the xUML Runtime writes information to the xUML service log. Depending on the log level of the service, this can be errors, warnings, general information, and low-level debug information (see Log Levels of the Service Log below).
The log files are very useful for debugging. If a problem with an xUML service occurs, check its service log for errors. Each incident will be recorded in chronological order.
Refer to Working With the Log Analyzer for more information on how to find these logs.
The following information is displayed in the xUML service log:
Log Item Property | Example / Description |
|---|---|
Time |
Timestamp of the log item in local server time. |
log.severity |
One of the log levels listed below. The log level defines which messages are logged. |
log.domain |
The error domain and code refer to the source of the error. The xUML Runtime uses a extensive list of error domains and codes. You can find all details on Log Errors. When developing a service, you can define your own error domains and codes, and log messages to the service log using the Logger adapter. Do not use the error domains and codes that are already used by the xUML Runtime. |
log.code | |
message |
A descriptive text giving some more details on the log item. The length of a log message is limited to 10.000 bytes on the PAS platform. Longer log entries will be truncated. Truncated messages indicate this by showing |
Log Levels of the Service Log
You can set the following log levels for each xUML service. The higher the log level, the more information is 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.
Log Level | Description | |
|---|---|---|
None | Logging is disabled. | |
Fatal | Logs fatal errors. | A fatal error means that the service cannot continue its normal execution, e.g. due to repository errors, system limitations like no more available threads or memory. These errors need the intervention of an administrator to solve the problem. |
Error | Logs fatal errors and other errors. | Errors other than fatal errors are not written if they are caught in the Designer service model, e.g. connection errors, wrong SQL statements, applying operations to invalid values, and so forth. If an error is caught, the modeler must take care of the error handling. |
Warning | Logs errors and warnings. | Warnings indicate unexpected but non-critical situations that do not interrupt normal operation. |
Info | Logs errors, warnings, and general information about your process steps and other service events. | This general information includes, for instance, which component is being started or stopped, loaded add-ons, licensing information, etc. |
Debug | Logs errors, warnings, general information, and low-level debug information. | In addition to log level Info, low-level debug information is written into an error file specified in the error message. Furthermore, the full adapter communication stream is written to the xUML service standard log. 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]
Related Content
Related Documentation: