Client behaviour when request target is unreachable or unstable

Problem:

1. Network failure (target machine not reachable).

2. Resource outage on target machine (e.g. no swap memory available).

3. 100% of CPU utilized in target machine.

Resolution:

The following would be the behaviour of the VBC Client process for the conditions in description above:

1. Network failure

   - Client will receive a CORBA::COMM_FAILURE exception. Can also receive CORBA::TIMEOUT exception if QoS timeout policies are set.

2. Server runs out of resources (memory, threads, file descriptors)

  - Client will receive a CORBA::NO_RESOURCES exception.

3. Server process is hanging due to lack of cpu availability

  - Client process would hang. Will receive a CORBA::TIMEOUT exception if QoS timeout policies are set. The details of above CORBA exceptions are provided in Appendix A of VBC 4.5 Programmer"s Guide.

If the application is witnessing a different behaviour on the Client side, then we would like to know the details of the scenario to provide an explanation.