Common problems

This section describes some of the problems that you might find.

ORB application hangs
One of the worst conditions is when the client, or server, or both, hang. If a hang occurs, the most likely condition (and most difficult to solve) is a deadlock of threads. In this condition, it is important to know whether the workstation on which you are running has more than one CPU, and whether your CPU is using Simultaneous Multithreading (SMT).
Starting the client before the server is running
If the client is started before the server is running, an error occurs when you run the client.
Client and server are running, but not naming service
An example of the error messages that are generated from this process.
Running the client with MACHINE2 (client) unplugged from the network
An example of the error messages that are generated when the client has been unplugged form the network.
Autonomic connection management issues

Parent topic: ORB problem determination