| Summary | The parameter "setDiagnostics" in orbixweb3.cfg does not work if the config file is included just before the OrbixJava config. |
|---|---|
| Article Number | 26558 |
| Environment | All platforms,Orbix3.3.10 |
| Question/Problem Description | When the standard "iona.cfg" file is used, the diagnostic level cannot be changed with the parameter "setDiagnostics" in orbixweb3.cfg, although it can be changed with the command line parameter "-DOrbixWeb.setDiagnostics=value". |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | ORBTHREE-857 |
| Cause | There's a known issue "ORBTHREE-857" with Orbix Java in parsing of the config file iona.cfg. If you take a standard iona.cfg file: >> cfg_dir = "/local1/users/khallig/orbix3310_actional/config/"; include cfg_dir "common.cfg"; include cfg_dir "orbix3.cfg"; include cfg_dir "orbixnames3.cfg"; include cfg_dir "orbixweb3.cfg"; << Due to the issue with the parser for Orbix configuration file, setDiagnostics in orbixweb3.cfg cannot change the diagnostic level in OrbixJava if orbixnames3.cfg is included just before orbixweb3.cfg. |
| Resolution | The issue will be fixed in V3.3.11 |
| Workaround | If the orbixweb3.cfg file is not the last file included in iona.cfg, then the setDiagnostics config variable is set and everything works fine. Just including a dummy include file (doesn't matter if it doesn't exist) will get around the issue, or else re-order the other include files to ensure orbixweb3.cfg isn't the last one included. |
| Notes | |
| Attachment |
| Created date: | 15 November 2011 |
|---|---|
| Last Modified: | 14 February 2013 |
| Last Published: | 17 November 2011 |
| First Published date: | 15 November 2011 |
#KnowledgeDocs
#Orbix
