Properties to use to enable ORB traces.
Attention: Do not enable tracing for normal operation,
because it might cause performance degradation. Even if you have switched
off tracing, FFDC (First Failure Data Capture) is still working, so
that only serious errors are reported. If a debug file is produced,
examine it to check on the problem. For example, the server might
have stopped without performing an ORB.shutdown().
You can use the following properties to enable the ORB traces:
- com.ibm.CORBA.Debug: This property turns on trace, message, or both. If you
set this property to trace, only traces are enabled; if set
to message, only messages are enabled. When set to true,
both types are enabled; when set to false, both types are
disabled. The default is false.
- com.ibm.CORBA.Debug.Output:
This property redirects traces to a file, which is known as a trace
log. When this property is not specified, or it is set to an empty
string, the file name defaults to the format orbtrc.DDMMYYYY.HHmm.SS.txt,
where D=Day; M=Month; Y=Year; H=Hour (24 hour format); m=Minutes;
S=Seconds. If the application (or Applet) does not have the privilege
that it requires to write to a file, the trace entries go to stderr.
- com.ibm.CORBA.CommTrace: This
property turns on wire tracing, also known as Comm tracing. Every
incoming and outgoing GIOP message is sent to the trace log. You can
set this property independently from Debug. This property is useful
if you want to look only at the flow of information, and you are not
interested in debugging the internals. The only two values that this
property can have are true and false. The default is false.
Here is an example of common usage:
java -Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.Debug.Output=trace.log -Dcom.ibm.CORBA.CommTrace=true <classname>
For rmic -iiop or rmic -idl, the following diagnostic tools are
available:
- -J-Djavac.dump.stack=1: This
tool ensures that all exceptions are caught.
- -Xtrace: This
tool traces the progress of the parse step.
If you are working with an IBM® SDK, you can obtain CommTrace
for the transient name server (tnameserv) by using the standard environment
variable
IBM_JAVA_OPTIONS. In a separate command session to
the server or client SDKs, you can use:
export IBM_JAVA_OPTIONS=-Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.Debug=true
The setting of this environment variable affects each Java™ process that is started, so use this variable
carefully. Alternatively, you can use the
-J option to pass
the properties through the tnameserv wrapper, as follows:
tnameserv -J-Dcom.ibm.CORBA.Debug=true