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

ORB problem determination

One of your first tasks when debugging an ORB problem is to determine whether the problem is in the client-side or in the server-side of the distributed application. Think of a typical RMI-IIOP session as a simple, synchronous communication between a client that is requesting access to an object, and a server that is providing it.

During this communication, a problem might occur in the execution of one of the following steps:

1. The client writes and sends a request to the server.
2. The server receives and reads the request.
3. The server executes the task in the request.
4. The server writes and sends a reply back.
5. The client receives and reads the reply.

It is not always easy to identify where the problem occurred. Often, the information that the application returns, in the form of stack traces or error messages, is not enough for you to make a decision. Also, because the client and server communicate through their ORBs, if a problem occurs, both sides will probably record an exception or unusual behavior.

This section describes all the clues that you can use to find the source of the ORB problem. It also describes a few common problems that occur more frequently.

• Identifying an ORB problem
  A background of the constituents of the IBM ORB component.
• Debug properties
  Properties to use to enable ORB traces.
• ORB exceptions
  The exceptions that can be thrown are split into user and system categories.
• Completion status and minor codes
  Two pieces of data are associated with each system exception, these are described in this section.
• Java security permissions for the ORB
  When running with a Java™ SecurityManager, invocation of some methods in the CORBA API classes might cause permission checks to be made that could result in a SecurityException.
• Interpreting the stack trace
  Whether the ORB is part of a middleware application or you are using a Java stand-alone application (or even an applet), you must retrieve the stack trace that is generated at the moment of failure. It could be in a log file, or in your terminal or browser window, and it could consist of several chunks of stack traces.
• Interpreting ORB traces
  The ORB trace file contains messages, trace points, and wire tracing. This section describes the various types of trace.
• Common problems
  This section describes some of the problems that you might find.
• IBM ORB service: collecting data
  This section describes how to collect data about ORB problems.

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