TroubleShooting: Object Request Broker (ORB) problems

There are times when one may find orbtrc.<date>.<time>.txt files in various locations without having turned on ORB trace (usually for a client).  Initially, one might think ORB trace has somehow been inadvertently turned on.  But in fact, these are ORB FFDC files.  Depending on the error(s) being reported and their frequency, the generation of these files can clutter a program’s working directory.

Facts about these orbtrc.txt files:

1.       They are NOT ORB trace files (generated from com.ibm.CORBA.Debug=true).

2.       They are ORB FFDC files used for reporting more serious exceptions that occur when tracing is NOT engaged.

3.       There is no capability for turning OFF these messages as their intention is to help report potentially serious problems without tracing.

4.       The files can be created by both full WebSphere Server entities (Dmgr, NodeAgent, AppServer) and also Java clients.

5.       The files will be created in the location from which the JVM (client or server) is launched.

6.       The following pages describe the creation of these orbtrc.DDMMYYY.HHmm.SS.txt files:

o   CORBA minor codes

o   Debug properties

Ways to manage orbtrc.txt files:

1.       Prevent the creation of the files.

• Redirect the file output to /dev/null or NUL
• Linux/Unix:  set com.ibm.CORBA.Debug.Output=/dev/null
• Windows:  set com.ibm.CORBA.Debug.Output=NUL
• NOTE:  the loss of important diagnostic information could result.
• NOTE:  com.ibm.ffdc.log=Suppress is not applicable to ORB FFDC because the ORB is actually a separate entity (shipped within the IBM JDK) from WebSphere, with its own separate logging/FFDC implementations.

2.       Redirect the files to a specific location.
The following options allow for the review of the FFDC exception data being generated and easy removal when desired.  All options involve setting the JVM property -Dcom.ibm.CORBA.Debug.Output to:

a.       A directory

• Allows easier monitoring of the files' creation.
• Keeps the FFDC files separate from other config/program/script files.
• Allows for a simple cronjob to remove ALL files easily and quickly.

b.       A single file

• e.g. ORB_FFDC_log
• Causes ALL ORB FFDC msgs to be written to that single file.
• If no path is given, this single file will reside where the JVM is launched.

c.       A combination of full path and file name.

• e.g. C:\WAS\client\logs\orb_ffdc.log
• Allows for a separate directory containing a single file with all the ORB FFDC information.