IBM Support

PI54461: APPLICATION SERVER PROCESS USES WRONG HOSTNAME TO COMMUNICATE STATUS TO NODE AGENT

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The node agent starts an application server and opens a listen
    on the port defined for was.status.socket using it's configured
    hostname as part of the launch process.  But, when the app
    server tries to communicate with the node agent, it uses the
    local host name of the system rather than the hostname the node
    agent is configured to use.  So, the application server can't
    notify the node agent that it has started.
    
    The app server will show this message:
    BBOO0220E: WSVR0121E: An exception occurred getting a socket
    for port <was.status.socket> on hostname local_hostname_of
    system with an IP address of ip_addr_oflocal_hostname_of system
    
    This FFDC is cut
    com.ibm.ws.runtime.component.ServerCollaborator.getStatusPort
    564
    
    A trace will show this failure:
    
    getStatusSocket:STATUS_CONNECT_IPADDR Exception:
    java.net.ConnectException: EDC8128I Connection refused.
    (errno2=0x76630291)
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at
    java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:381)
     at java.net.PlainSocketImpl.connectToAddress
    (PlainSocketImpl.java:243)
     at java.net.PlainSocketImpl.connect
    (PlainSocketImpl.java:230)
     at java.net.SocksSocketImpl.connect
    (SocksSocketImpl.java:377)
     at java.net.Socket.connect(Socket.java:539)
     at java.net.Socket.connect(Socket.java:488)
     at java.net.Socket.<init>(Socket.java:385)
     at java.net.Socket.<init>(Socket.java:228)
     at
    com.ibm.ws.runtime.component.ServerCollaborator.getStatusSocket
    (ServerCollaborator.java:543)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Network Deployment V7.0, 8.0, 8.5.5, *
    *                  and 9.0                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: A custom-defined node agent hostname    *
    *                      results in the server failing to        *
    *                      communicate status to the node agent    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WAS Network Deployment communications logic includes an
    assumption that the node agent is located on the same physical
    system as the application server(s).  However, that logic does
    not account for the possibility that the network configuration
    will be defined in a way that the node agent is on a separate
    virtual address, in which "localhost", as called from the
    server, does not resolve to the node agent's address.  In this
    case, the server will not successfully communicate its startup
    state to the node agent, and the node agent will be unable to
    effectively monitor the server's status.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI54461

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-18

  • Closed date

    2016-09-23

  • Last modified date

    2017-05-01

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI46199

       UP17/04/24 P F704

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 December 2021