IBM User Guide for Java V7 on Windows > Troubleshooting and support > Problem determination > ORB problem determination

IBM ORB service: collecting data

This section describes how to collect data about ORB problems.

If after all these verifications, the problem is still present, collect at all nodes of the problem the following information:

• Operating system name and version.
• Output of java -version.
• Output of java com.ibm.CORBA.iiop.Version.
• Output of rmic -iiop -version, if rmic is involved.
• ASV build number (WebSphere Application Server only).
• If you think that the problem is a regression, include the version information for the most recent known working build and for the failing build.
• If this is a runtime problem, collect debug and communication traces of the failure from each node in the system (as explained earlier in this section).
• If the problem is in rmic -iiop or rmic -idl, set the options: -J-Djavac.dump.stack=1 -Xtrace, and capture the output.
• Typically this step is not necessary. If it looks like the problem is in the buffer fragmentation code, IBM service will return the defect asking for an additional set of traces, which you can produce by executing with -Dcom.ibm.CORBA.FragmentSize=0.

A testcase is not essential, initially. However, a working testcase that demonstrates the problem by using only the Java™ SDK classes will speed up the resolution time for the problem.

• Preliminary tests
  The ORB is affected by problems with the underlying network, hardware, and JVM.

Parent: ORB problem determination

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.