Problem:
- Product Name: VisiBroker for Java
- Product Version: 4.x, 5.x, and 6.x
- Product Component: Diagnostic Logging
- Platform/OS Version: All
This article discusses the meaning and acceptible range of values for the following diagnostic properties:
- vbroker.orb.logLevel
- vbroker.poa.logLevel
- vbroker.naming.logLevel
- vbroker.security.logLevel (see Note #1 below)
Resolution:
All of the standard Visibroker logLevel properties shown above have a numeric value as well as a corresponding text value. Either one can be used to set the property (see exception in Note #1 below). The description explains under which situations would information be logged.
The acceptable values for the logLevel properties are as follows:
- EMERG or 0
- System is unusable. A panic condition (default).
- ALERT or 1
- A condition that should be corrected immediately, such as a corrupted system database.
- CRIT or 2
- Critical conditions, such as hard device errors.
- ERR or 3
- Error conditions.
- WARNING or 4
- Warning conditions.
- NOTICE or 5
- Conditions that are not error conditions, but that may require special handling.
- INFO or 6
- Informational
- DEBUG or 7
- Debug messages meant to be understood only by developers. These are not internationalized. This value is recommended for submitting diagnostic output to Borland for support and analysis.
Notes:
- vbroker.security.logLevel uses ONLY the numeric format of the log level values (0-7).
- Any numeric value higher than 7 is also considered DEBUG.
- The text values are NOT case-sensitive.
- Not all logLevels are used by all product components. If a specific logLevel is not meaningful it will default to the next lowest logLevel.
#VisiBroker
#Security
