IBM Support

PK14391: SERVER PROCESS DOES NOT COMMUNICATE STATUS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The server fails to open a socket on the localhost, which
    it uses to communicate status to the launching process.
    This problem can manifest as the inability to control
    a WAS Server from the Windows Services panel, for example.
    The problem exist whenever a message like the following
    appears in the SystemOut.log file:
    
    21-10-05 10:35:49:364 CEST  0000000a ServerCollabo E
      WSVR0121E: An exception occurred getting a socket for port
      14618 on hostname ccz1cs0002 with an IP address of
      10.28.17.20.
    java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(...)
    at java.net.PlainSocketImpl.doConnect(...)
     ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere Application Server    *
    *                 V6.02 utilizing a network or firewall        *
    *                 configuration that prohibits opening a       *
    *                 socket on the server status port using the   *
    *                 actual IP address of the host server, but    *
    *                 allows opening sockets on the loopback       *
    *                 (localhost) address.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: After starting an application server,   *
    *                      WebSphere Application Server does not   *
    *                      indicate the server to be started, but  *
    *                      the server operates as designed.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Server is unable to open socket port on the actual IP
    address of the machine hosting the server process (as
    opposed to the loopback address.)
    

Problem conclusion

  • Apply this APAR to enable WebSphere Application Server to
    open a socket on the status port using the loopback IP address
    to communicate server status. An alternate resolution is to
    modify the network or firewall configuration to allow opening
    sockets over the status port using the host machine IP address.
    
    The fix for this APAR is currently targeted for inclusion
    in fixpack 6.0.2.5.
    Please refer to the recommended updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK14391

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    60W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-11-01

  • Closed date

    2005-11-21

  • Last modified date

    2014-10-13

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

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

    PK21567

Modules/Macros

  • RUNTIME
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022