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:
- Operating system name and version.
- Output of java -Xgcpolicy:metronome -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.