IBM Support

PI92079: DUPLICATE PORTS ARE ASSIGNED WHEN THE NODE USES DIFFERENT HOST ALIAS IN SAME HOST MACHINE WHERE THE DMGR IS RUNNING

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • The server unique port generation algorithm is based on the
    machine host IP.  If the port has been used in the dmgr host
    machine, it will keep increasing by 1 until an unique port is
    found. However, if appserver node and dmgr have different host
    aliases or host IPs within the same machine they will be treated
    as different host machines and duplicate ports can be assigned.
    

Local fix

  • Use same host alias/host ip on dmgr and node within same host
    machine.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Duplicate server ports are assigned     *
    *                      during server creation when a           *
    *                      deployment                              *
    *                      manager and node are on the same        *
    *                      machine                                 *
    *                      and using host aliases.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The server unique port generation algorithm uses the host IP
    address as a key to é ádetermine whether the node and deployment
    manager are in the same host é ámachine.  é áIf the node host IP
    address
    is same as the deployment manager's address then unique ports
    will
    be generated for new servers on the node.  é áHowever, if the
    server
    node and deployment manager use different host aliases within
    the é ásame machine, the node would be treated as a different ho
    machine and é áduplicate server ports could be assigned during
    server é ácreation. It could cause the following port conflict
    error é ámessage when starting the server.
    [1/30/18 13:34:38:520 EST] 00000001 TCPPort  é á  é á  é á E
     é á é áTCPC0003E:
    TCP
    Channel é áTCPInboundChannel_jm.Default_JM_SSL_Port_Connector_Na
     é á
     é á  é á  é á
    initialization failed.  é áThe socket bind failed for host  é á
     é áachflisbatch-cc1-qa2-wsdm.fras.frb.org and port 9421.
     é áThe é áport
    may already be in use.  é á  é á  é á
    

Problem conclusion

  • It is a bug in the unique server port generation algorithm
    where é áthe node should not be necessarily treated as a differe
    host machine even though it has a different host name and IP fro
    that of the deployment manager.  é áIt should also check if mult
    network interfaces are configured in the é ámachine.  é áIf mult
    network interfaces contain both node and deployment manager host
    IP addresses, it means both the node and the deployment manager
    are in the same machine. é á
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.14/9.0.0.8.  é áPlease refer to the é áRecommended Up
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI92079

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-04

  • Closed date

    2018-02-05

  • Last modified date

    2018-04-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI92079

Modified date: 13 April 2018


Translate this page: