Exceptions triggering automatic failover

The following is a list of exceptions that the EJB workload management will react to. Depending on the exception, it will redirect the failed request to another cluster server: If the root exception org.omg.CORBA.COMM_FAILURE or the org.omg.CORBA.NO_RESPONSE exception is thrown, their return value will determine whether automatic failover occurs: With a COMPLETION_STATUS of COMPLETED_NO, automatic failover occurs because the request was not completed. With a COMPLETION_STATUS of COMPLETED_YES, failover does not occur because the request was successfully completed. With a COMPLETION_STATUS of COMPLETED_MAYBE, automatic failover does not occur. The workload management plug-in cannot verify whether the request was completed. In this situation, the client application must anticipate a failure and retry the request. The workload management plug-in then attempts to direct the request to a surviving cluster member. org.omg.CORBA.COMM_FAILURE

This exception is thrown by the ORB when a communications failure occurs. Any current transactions are rolled back and non-transactional requests are redone. org.omg.CORBA.NO_RESPONSE

This exception is thrown by the ORB when a communication failure occurs after a connection has been established, for example because a timeout occurs before getting a response. org.omg.CORBA.TRANSIENT

This exception is thrown by the ORB when a connection could not be established when the application tried to invoke a request.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.