Configuring Logging
This section provides information for using logging for the Solace Java RTO API.
The Solace Java RTO API uses Java's default java.util.logging framework. Log levels in the Solace Java RTO API correspond with certain log levels in the Solace C API. The table below shows the mapping of log levels between the APIs.
| Solace Java RTO API Level | Matching Solace C API Level | Description |
|---|---|---|
|
Severe |
Critical |
These log levels are reserved for internal errors and should be a cause for investigation. Contact Solace for log events at this level. |
|
Error |
||
|
Warning |
Warn |
Indicates an application error (for example, invalid parameters passed in or unsupported use of the APIs). |
|
Info |
Notice |
Reserved for unusual events that do not indicate any error, but they are unexpected and might need investigation. |
|
Fine |
Info |
Typically used for state changes at a high level (for example, connect/disconnect/reconnect). |
|
Finest |
Debug |
This log level is voluminous and typically requires us to interpret. |
When a log level is set at a given level, all log events with log level less severe than the selected level are filtered out; all log levels equally or more severe are included. For example, if the Warning log filter level is selected, only Warning and Severe events are included. In contrast, if the Fine log filter level is selected, Fine, Info, Warning, and Severe events are included, and the Finest level is filtered out.
Related Samples
You can see the example in the Logging.java sample file that demonstrates how to work with logs generated by the API.
You can find these examples on Solace Developers.