Setting a time limit for the completion of RMI/IIOP enterprise bean requests

For an application to compensate for or retry an expired enterprise bean invocation, the application must:

• Be running outside of the current global transaction, and
• Catch the org.omg.CORBA.COMM_FAILURE exception.

The following example, which is a snippet of code that is running outside an atomic transaction, illustrates the steps an application must perform if you want that application to compensate for or retry an expired enterprise bean invocation:

// This method runs outside a global transaction.       
public Data callingMethod() throws … {        
     try{
            InitialContext con = new InitialContext(); 
            EJBHome home con.lookup(...);    
            CalledBean cb = home.create();   

     } catch (org.omg.CORBA.COMM_FAILURE cf1){
        // The home create could timeout, so put retry or 
        // compensation logic here. 

     } catch( CreateException cx){  
                 throw new ...  
     } catch( NamingException nx){
                 throw new ...  
     } catch(RemoteException ex){ 
                 throw new ... 
     }
     try{
 		     	cb.calledMethod(…);

     } catch (org.omg.CORBA.COMM_FAILURE cf2){                
// The calledMethod could timeout, so put retry or 		   
// compensation logic here. 
     } catch( … ){ 
     			… 	
     }       
}  	

// This method can run in a global transaction.       
private void calledMethod(String strKey) throws … { 
      try{ 
             // business logic here 
      } 
      catch ( … ){  
                  throw new ...  
      }       
}