PQ75181: DURING CUSTOMIZATION OF WEBSPHERE 5.0 GENERATED MEMBERS BBOTCPIPAND BBOTCPID ARE MISSING DEFINITIONS FOR SOME TCP/IP PORTS

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
During the Base Application Configuration of WebSphere for
z/OS V5, the install instructions (BBOSSINS) Manual Step 7
gives instructions to reserve certain ports in the TCP/IP
settings.  The dialog also generate mamber BBOTCPIP (for
Base App Server Node config), which have the TCP/IP
statements that are to be added to the PORT section of
the file referenced by the DD Statement in for the
TCP/IP Profile in the TCP/IP startup procedure.
In the Base App configuration, the information in BBOSSINS
manual step 7, lists 8 ports which were defined through the
dialog panels.  The information in member BBOTCPIP however
only has statements for 2 of the 8 ports.  There should be
6 statements generated in the BBOTCPIP member, as shown in
the Local Fix section of this APAR.
.
During the Deployment Manager Node Configuration of
WebSphere for z/OS V5, the install instructions
(BBOCCINS) Manual Step 3 gives instructions to reserve
certain ports in the TCP/IP settings.  The dialog also
generate mamber BBOTCPID (for Deployment Manager Node
config).  which have the TCP/IP statements that are to
be added to the PORT section of the file referenced by
the DD Statement in for the TCP/IP Profile in the TCP/IP
startup procedure.
In the Deployment Manager Node Configuration, the information
in BBOCCINS manual step 3, lists 9 ports which were defined
through the dialog panels.  The information in member
BBOTCPID however only has statements for 2 of the 9 ports.
There should be 7 statements generated in the BBOTCPID
member, as shown in the Local Fix section of this APAR.
.
MD17106
TCPIP minor code 744C7246 indicates "permission denied"
Additional Symptoms:
BBOO0040E Function bind() failed with RV=-1, RC=111,
          RSN=744C7246, [EDC5111I Permission denied.
          (errno2=0x744C7246)]
BBOO0160E Function bind() failed with RV=-1, RC=111,
          RSN=744C7246, [EDC5111I Permission denied.
          (errno2=0x744C7246 ]hostname/ip: 0.0.0.0
BBOO0142E Socket bind() for Server=XYZ123 to Port=50121 failed
          with RV=-1, RC=111, RSN=744C7246,  EDC5111I
          Permission denied. (errno2=0x744C7246)
ADMC0015W: The SOAP connector failed to start with exception:
          EDC5111I Permission denied. (errno2=0x744C7246)
general socket exception; java.net.BindException:
           EDC5111I Permission denied. (errno2=0x744C7246)
     at java.net.PlainSocketImpl.socketBind(Native Method)
     at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:360)
     at java.net.Socket.bind(Socket.java:524)
     at java.net.Socket.<init>(Socket.java:333)
     at java.net.Socket.<init>(Socket.java:179)
     at com.ibm.ws.management.discovery.transport.
        .TcpMessenger.openSocket(TcpMessenger.java:209)
Fatal error starting broker:
     com.ibm.disthub.spi.ServiceStartupException:
     &#65412;-1039695125!tcp!53679!java.net.BindException:
     EDC5111I Permission denied.
     (errno2=0x744C7246)!&#65409; wrapped exception: null     "
Local fix
Base Application Configuration Local Fix
.
If the defaults are taken for port assignments during the
Installation and Customization Dialogs, AND those ports that
are then identified in 'Manual Step 7' of BBOSSINS are NOT
in use on the system, (or have the possibility of being used
by some other application), then reserving the ports would
not be necessary.
.
If you want to reserve the ports listed in Step 7, we have
tested the following format of the definition of the ports.
.
Using the following information from Step 7:
7.  Update TCP/IP by reserving the following ports for
    WebSphere for z/OS:

        Daemon IP port             - 5655
        Daemon SSL port            - 5656
        SOAP JMX Connector port    - 8880
        DRS Client Address port    - 7873
        ORB port                   - 2809
        ORB SSL port               - 0
        HTTP port                  - 9080
        HTTP SSL port              - 9443
  .
 Information that should be in member BBOTCPIP
 .
 8880 TCP BBOS001      ; SOAP JMX Connector port
 2809 TCP BBOS001      ; ORB port
 9080 TCP BBOS001      ; HTTP port
 9443 TCP BBOS001      ; HTTPS port
 5655 TCP BBODMNB      ; daemon port
 5656 TCP BBODMNB      ; daemon SSL port
.
(where BBOS001 is the server specific short name,
  and BBODMNB is the daemon jobname)
.

Deployment Manager Node Configuration Local Fix
.
If the defaults are taken for port assignments during the
Installation and Customization Dialogs, AND those ports that
are then identified in 'Manual Step 3' of BBOCCINS are NOT
in use on the system, (or have the possibility of being used
by some other application), then reserving the ports would
not be necessary.
.
If you want to reserve the ports listed in Step 3, we have
tested the following format of the definition of the ports.
.
Using the following information from Step 3:
3.  Update TCP/IP by reserving the following ports for
    WebSphere for z/OS:
.
    Daemon IP port               - 5755
    Daemon SSL port              - 5756
    SOAP JMX Connector port      - 8879
    CELL DISCOVERY ADDRESS port  - 7277
    DRS CLIENT ADDRESS port      - 7989
    ORB port                     - 9809
    ORB SSL port                 - 0
    HTTP port                    - 9090
    HTTP SSL port                - 9043
.
Information that should be in member BBOTCPID
.
 8879 TCP BBODMGR     ; SOAP JMX Connector port
 7277 TCP BBODMGR     ; Cell Discovery port
 9809 TCP BBODMGR     ; ORB port
 9090 TCP BBODMGR     ; HTTP port
 9043 TCP BBODMGR     ; HTTPS port
 5755 TCP BBODMNC     ; daemon port
 5756 TCP BBODMNC     ; daemon SSL port
.
(where BBODMGR is the server specific short name,
 and BBODMNC is the daemon jobname)
.
.
Add Node Configuration Local Fix
.
When you use the addNode.sh script to 'fererate' into the
Deployment Manager, the following ports will need to reserved
in TCP/IP.
.
8878 TCP BBON001     ; SOAP JMX Connector port
7272 TCP BBON001     ; Node Discovery port
(SEE NOTE2)          ; Node Multicast Discovery port
2809 TCP BBON001     ; node agent's ORB port
9810 TCP BBOS001     ; base server's ORB port
.
Where BBON001 is the nodeagent's short name and BBOS001 is the
short name of the base app server whose node is being added to
the Deployment Manager cell.
.
NOTE: The addNode process introduces a special utility server
      to the node.  This utility server is called a nodeagent
      and exists to support administrative functions on the
      node.  By default the nodeagent takes over ORB port 2809.
      Note that WebSphere z/OS the ORB port doubles as the
      INS CosNaming bootstrap port.  By default, this port was
      assigned to the base server.  Normally you want the
      nodeagent to be the INS CosNaming bootstrap point for the
      entire node, so that RMI/IIOP clients that do not override
      the INS CosNaming bootstrap defaults can access EJBs on
      any server on that node.  In order for the nodeagent to
      take over port 2809, the base server must be assigned a
      new ORB port.  The default new ORB port for the base
      server is 9810.
If any of the above ports are reserved with the wrong user id
you may experience the following error message and errno code.
.
EDC5111I Permission denied. (errno2=0x744C7246)
.
The 7246 erno code above indicates that:
JRPORTACCESSAUTH User does not have authority to access this
port.
.
NOTE 2: (03/02/05)
The list of port reservations used to include:
.
5000 TCP BBON001     ; Node Multicast Discovery port
.
which has now been removed from this apar for the following
reason:
.
Multicast uses the UDP protocol and not the TCP protocol.
In Websphere multiple address spaces bind to the multicast
port, but you can not reserve a UDP port for multiple
address spaces in TCP/IP.
.
Having the Node Multicast Discovery port reserved as a TCP
port will not cause a problem with WebSphere discovery process,
but it is unnecessary.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: During installation if WebSphere V5.0,  *
*                      generated member BBOTCPIP is missing    *
*                      definitions for some TCP/IP ports.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Dialog generated jobs BBOTCPIP, BBOTCPID have either missing
or incorrect ports reserved. These jobs need to be corrected and
instructions need be provided as to how to correctly reserve
TCP/IP ports.
Problem conclusion
The dialog instructions and skeletons have been updated to have
TCP/IP ports correctly reserved.

APAR PQ75181 is associated with SERVICE LEVEL W500103 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ75181
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 2003-06-12
Closed date 2003-08-01
Last modified date 2006-03-27

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 UQ79131    UP03/08/08 I 1000

  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: swg1PQ75181.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 #: PQ75181
IBM Group: Software Group
Modified date: Mar 27, 2006