PQ69951: WEBSPHERE DOES NOT BIND THE ORB COMMUNICATION PORTS TO A PARTICULAR IP ADDRESS/HOSTNAME WHEN THEY ARE SPECIFIED.

 A fix is available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
WAS 4.0.x - Customer is trying to run multiple instances of
Websphere 4.0.3 on the same machine using the same CORBA
communication port numbers for both instances. The two
instances are setup on two separate virtual IP addresses/hostnam
es.  When the customer tries to start the two instances of WAS
using the property com.ibm.CORBA.LocalHost (= to an IP Address)
and com.ibm.ejs.sm.adminServer.nodeName (= to shortname or fully
qualified domain name of the machine) the CORBA ports do not
bind to those specific IP address/hostname only.  The CORBA
ports bind to all IP addresses/hostnames defined on that
machine.  The orb team has created a test fix called
ORBtest0114_Test.jar that addressed this issue.  I am creating
an official apar to address this problem.
Local fix
Use unique port numbers for each instance of WAS on the machine.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of    *
*                 multiple NetWork Interface cards in a box.   *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere ORB binds primary IP          *
*                      address or hostname with RMI-IIOP       *
*                      communication ports although user       *
*                      has explicitly set the localhost to     *
*                      be a secondary (virtual) IP or          *
*                      hostname.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
User might have or use more than one network interface card in
a box. When user intends to set or run Websphere Application
Server on a secondary (Virtual) IP or hostname, user might
observe that WebSphere is still using the primary IP or
hostname as default on some of the RMI-IIOP communication
ports.
Problem conclusion
When WebSphere ORB creates a new socket, it now binds each
RMI-IIOP communication port to the specific IP or hostname set
by user. To achieve the correct behavior, user needs to add the
following ORB properties to all WebSphere client and Server
processes which uses RMI-IIOP.

I. Add these entries into admin.config file for adminServer
   com.ibm.CORBA.LocalHost=<IP Address or hostname>
   com.ibm.ejs.sm.adminServer.bootstrapHost=<IP address or
hostname>
# note: you need to get fix 
PQ69956 before using this
property setting.otherwise you won't be able to start
adminServer.
   com.ibm.ejs.sm.adminServer.bootstrapPort=yyyy
# default port value is 900
   com.ibm.ejs.sm.adminServer.lsdHostName=<IP Address or
hostname>
   com.ibm.ejs.sm.adminServer.lsdPort=xxxx
# default port value is 9000
   com.ibm.CORBA.ListenerPort=zzzz
# if this property is not add, the port value will be
dynamically assigned
   com.ibm.ejs.sm.adminServer.nodeName=<short DNS name>

II. Add these entries to the Application Server's command line
argument of JVM Advanced settings via adminConsole
   -Dcom.ibm.CORBA.LocalHost=<IP Address or hostname>
   -Dcom.ibm.CORBA.BootstrapHost=<IP Address or hostname>
# IP Address of hostname should be the adminServer process's
IP Address or hostname
   -Dcom.ibm.CORBA.BootstrapPort=yyyy
# where yyyy should be matching to the bootstrap port value
set in admin.config
Note: the ports, xxxx, yyyy, and zzzz should be unique and valid

III. Taking the advantage of using Virtual IP address (VIP),
you can add the following properties to JAVA command to allow
your client to run on a specified hostname/IP address instead of
on the default primary hostname/IP address.

A) Add CORBA properties to the adminclient.bat/sh for
adminclient
-Dcom.ibm.CORBA.LocalHost=<hostname or IP>
-Dcom.ibm.CORBA.ListenerPort=aaaa
For example:
%JAVA_HOME%\bin\java -Dcom.ibm.CORBA.LocalHost=nic3.us.ibm.com
-Dcom.ibm.CORBA.ListenerPort=11002 -Xms19m ....
%JAVA_HOME%\bin\javaw
-Dcom.ibm.CORBA.LocalHost=nic3.us.ibm.com
-Dcom.ibm.CORBA.ListenerPort=11002 -Xms19m ....

B) Add  CORBA properties to the XMLConfig.bat/sh
-Dcom.ibm.CORBA.LocalHost=<hostname or IP>
-Dcom.ibm.CORBA.ListenerPort=bbbb
For example:
%JAVA_HOME%\bin\java %CLIENTSAS%
-Dcom.ibm.CORBA.LocalHost=nic3.us.ibm.com
-Dcom.ibm.CORBA.ListenerPort=11003

C) Add CORBAproperties to WSCP.bat/sh
-Dcom.ibm.CORBA.LocalHost=<hostname or IP>
-Dcom.ibm.CORBA.ListenerPort=cccc
For example:
%JAVA_HOME%\bin\java %WSCPCLIENTSAS%
-Dcom.ibm.CORBA.LocalHost=nic3.us.ibm.com
-Dcom.ibm.CORBA.ListenerPort=11004

D) Add CORBA properties to stand-alone EJB client
-Dcom.ibm.CORBA.LocalHost=<hostname or IP>
-Dcom.ibm.CORBA.ListenerPort=ddddd
For example:
$JAVA_HOME/bin/java -Dcom.ibm.CORBA.LocalHost=nic3.us.ibm.com
-Dcom.ibm.CORBA.ListenerPort=11004
Temporary fix Comments
APAR information
APAR number PQ69951
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-01-16
Closed date 2003-02-18
Last modified date 2003-02-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ORB          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69951
IBM Group: Software Group
Modified date: Feb 27, 2003