Debug properties

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:
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:
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


© Copyright IBM Corporation 2005, 2010. All Rights Reserved.
© Copyright Sun Microsystems, Inc. 1997, 2007, 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information center is powered by Eclipse technology. (http://www.eclipse.org/)