Configuration options for object request broker (ORB) interoperability with WebSphere® Application Server V3.5.x

Technote (FAQ)
Problem
Problems configuring WebSphere Application Server to interoperate with other CORBA object request brokers for enterprise bean applications can result in errors, such as:
- java.net.ConnectException: A remote host refused an attempted connect operation
- org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: No

Several configuration options are available that can help to resolve these problems.
Solution
Settings included in the "Command Line Arguments" of Application Server that need to be configured:
-Dcom.ibm.CORBA.requestRetriesCount=
-Dcom.ibm.CORBA.requestRetriesDelay=

Notes:
  • These settings do not go into the admin.config file because that would negatively impact the function of the administration server process.
  • Values for these two fields need to be adapted to the needs of the application.
  • This solution was configured with WebSphere Application Server V3.5.3
The following example was used by one customer when configuring interoperation with Orbix:
-Xmx64m -Dcom.ibm.CORBA.requestRetriesCount=9
-Dcom.ibm.CORBA.request.RetriesDelay=500 -classpath
/wasapp/QA/illustrations/servlet/XML_Parser_level_2.jar:/wasapp/QA/illustrations/servlet/DOM_Level_2_Parser.jar:/wasapp/QA/illustrations/servlet/JDOM.jar
Historical Number
PMR 09137
344
000











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, EJB Container
Operating system(s): Multi-Platform
Software version: 3.5
Software edition: Standard, Advanced
Reference #: 1063333
IBM Group: Software Group
Modified date: 2004-01-23