CORBA COMM_FAILURE error occurs when restarting an application server
 Technote (FAQ)
 
Problem
After restarting an Application Server, you receive a CORBA COMM_FAILURE error in the stdout file.
 
Cause
When the server is restarted, the port it was listening on for Object Request Broker (ORB) communications changed. The port is assigned dynamically when the server starts. If the new port is unavailable, the following communication failure occurs:

04-02-2004 3:00:08 PM ERROR (LACSDGenericAction.java:261) - CORBA COMM_FAILURE 3 No; nested exception is:
org.omg.CORBA.COMM_FAILURE:   minor code: 3  completed: No java.rmi.MarshalException: CORBA COMM_FAILURE 3 No; nested exception is:
org.omg.CORBA.COMM_FAILURE:   minor code: 3  completed: No          
org.omg.CORBA.COMM_FAILURE:   minor code: 3  completed: No
at
com.ibm.CORBA.iiop.HTTPConnection.send(HTTPConnection.java:447)
at com.ibm.CORBA.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:515)
at
com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.java:748)
at
com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.java:880)
at
com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:902)
at
com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:412)
at
org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:258)
at
org.lacsd.reporting.dao.ejb._ReportingParametersDAOHome_Stub.create(_ReportingParametersDAOHome_Stub.java:207)
at
org.lacsd.rdx.process.ReportParametersPO.getDynamicParams(ReportParametersPO.java:125)

 
Solution
Define the port statically so that when the server restarts, it can talk to the same port.

  1. Add the following line to the admin.conf file:

    com.ibm.CORBA.ListenerPort=<static port number>

  2. Restart the server.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Object Request Broker (ORB)
Operating system(s): HP-UX
Software version: 4.0.7
Software edition:
Reference #: 1170502
IBM Group: Software Group
Modified date: Jun 25, 2004