PQ86647: W502002 NODEAGENT REFERS TO UNEXPECTED PORT. BOOTSTRAP ADDRESS INCREMENTS TO NEXT AVAILABLE FREE PORT NOT TO SPECIFIED PORT

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The customer want to install a new WebSphere Network
Deployment System.  They specified  the new Network
Deployment Application Server with new
ORB/IIOP/Bootstrap Port of  9542.
..
The Our federation job BBOWADDN has the following input:
..
BPXBATCH SH +
  /WebSphere/WASCONFT/APPL+
 /AppServer+
  /bin/addNode.sh +
  K001- my.domain.name +
  9510 +
  -includeapps +
  -shortname MY_SHORT_NAME +
  -soapport 9520 +
  -orbport 9522 +
  -orbsslport 0 +
 -discoveryport 9524 +
  -mcdiscoveryport 9525 +
  -drsclientport 9521 +
  -baseserverorbport 9542 +
 ..
The jobs ends with RC=0 and with a message stating
"has been successfully federated"
..
The output from node agent server shows:
..
BBOO0222I ADMC0013I:
                       SOAP connector available at port 9520
BBOO0222I ADMC0026I:
                       RMI Connector available at port 9522
 (Which is correct)
..
The output from application server shows:
 ..
BBOO0222I ADMC0013I:
                     SOAP connector available at port 9540
BBOO0222I ADMC0026I:
                     RMI Connector available at port 9523
Which should be port 9542 as specified in the
Federation output.
..
The checked the system and verified that ports
requesting were free using the 'netstat' command.
..
 Base server ORB port
    Port for IIOP requests which acts as the bootstrap port
    for this server and also as the port through which the
   ORB accepts IIOP requests. Port value cannot be 0.
..
Note:
  The add node operation creates the nodeagent
   administrative server with a default ORB port  equivalent
   to the INS CosNaming default bootstrap port. Because
   this same port was previously used  by  the node's initial
  base server, the initial base server's ORB port must change
   to a new port value.
..
  The default value to which the application server's ORB
   port is set is 9810. If you configure multiple cells that
   intersect the same systems, use of the default value will
   cause a port conflict between these cells. This option helps
   you set the port number in case port 9810 was previously
  assigned.
..
 WebSphere check if the application server's bootstrap port
 value is 2809 and if so, change it to the configured port or
 9810 by default. In your case, the app server's bootstrap
 port was not 2809, so the check did not apply and it was
 assigned a unique port, since the NA took 9522.
..
Local fix
..
The customer got around problem by using the AdminConsole
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Application Server on startup does not  *
*                      listen on the Base Server ORB Listener  *
*                      Port configured via the BBOWADDN job.   *
*                      The job specified the argument          *
*                      -baseServerOrbPort xxxx whereas output  *
*                      from the Application Server indicates   *
*                      BBOO022I ADMC0026I: RMI Connector       *
*                      available at port yyyy                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Customization Dialog to federate a Base Application Server
Node provides an option to change the application server's ORB
port to avoid port conflicts if the default - 9810 has been
configured already. The federation utility is not setting the
port correctly based on the configured value passed as an
argument to the addNode.sh script in BBOWADDN.
Problem conclusion
Modified the Node federation utility to correctly set the
configured port.

APAR PQ86647 is associated with SERVICE LEVEL W502007 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ86647
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-03-25
Closed date 2004-04-28
Last modified date 2004-05-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ87899    UP04/05/03 P F404

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ86647.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ86647
IBM Group: Software Group
Modified date: May 5, 2004