| Summary | How to configure Orbix 3 logging level. |
|---|---|
| Article Number | 34530 |
| Environment | Orbix 3.x All supported platforms |
| Question/Problem Description | How to configure Orbix 3 logging level. How to set the Orbix 3 diagnostic level. Configuring Orbix 3 logging Configuring Orbix 3 diagnostic output |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | The level of detail reported by the Orbix 3 C Daemon can be specified with the configuration variable "IT_DIAGNOSTICS_LEVEL".
The variable "IT_DIAGNOSTICS_LEVEL" can be set in the "common.cfg" configuration file, or by calling SetConfigValue() in the application. Additionally, an Orbix 3 C application's diagnostic level can be similarly set by calling "CORBA:ORB:setDiagnostics()". Orbix 3 C supports three settings: "0", "1", or "2". - Diagnostic level "0" reports no diagnostic information. - Diagnostic level "1" (Default) reports diagnostic information each time a connection is opened or closed. - Diagnostic level "2" reports diagnostic information for every request or reply that enters or leaves the application. The level of detail reported by Orbix 3 Java can be specified with the configuration variable "setDiagnostics", which supports the range from 0 (No diagnostic information) to 255 (Full diagnostic information). By default, this is set to "1". The Orbix 3 Java Daemon's diagnostic level can be at runtime with the Daemon's menu. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 05 September 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 05 September 2012 |
| First Published date: | 05 September 2012 |
#KnowledgeDocs
#Orbix
