IBM Support

PI49224: TCPIP STACK EVENTS (SUCH AS RESTART) CAN CAUSE PROBLEMS WITH CAE SERVER, CAN FILL SERVER LOG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the TCPIP stack on the mainframe stops for any reason, the
    CAE Server will not function correctly after a restart, and the
    CAE Server log can fill up with java stack traces relating to
    RMI:
    .
    Aug 11, 2015 3:14:12 PM
    sun.rmi.transport.tcp.TCPTransport$AcceptLoop
    executeAcceptLoop
    WARNING: RMI TCP Accept-0: accept loop for
    ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=3445] throws
    Throwable occurred: java.net.SocketException: EDC5122I
    Input/output error.
     at java.net.PlainSocketImpl.socketAccept(Native Method)
     at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:449)
     at java.net.ServerSocket.implAccept(ServerSocket.java:473)
     at
    com.rocketsoft.net.RC4ServerSocket.accept(RC4ServerSocket.java:
    43)
    at
    sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(
    TCPTransport.java:381)
    at
    sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.j
    ava:353)
    at java.lang.Thread.run(Thread.java:736)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor z/OS.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the TCPIP stack on the mainframe     *
    *                      stops for any reason, the CAE Server    *
    *                      will not function correctly after a     *
    *                      restart, and the CAE Server log can     *
    *                      fill up with java stack traces          *
    *                      relating to RMI:                        *
    *                      Aug 11, 2015 3:14:12 PM                 *
    *                      sun.rmi.transport.tcp.TCPTrans          *
    *                      port$AcceptLoop executeAcceptLoop       *
    *                      WARNING: RMI TCP Accept-0: accept loop  *
    *                      for ServerSocket addr=0.0.0.0/0.0.0.0,  *
    *                      port=0,localport=3445  throws           *
    *                      Throwable occurred: java.net.           *
    *                      SocketException: EDC5122I               *
    *                      Input/output error.                     *
    *                       at java.net.PlainSocketImpl.           *
    *                      socketAccept(Native Method)             *
    *                       at java.net.PlainSocketImpl.           *
    *                      accept(PlainSocketImpl.java:449)        *
    *                       at java.net.ServerSocket.              *
    *                      implAccept(ServerSocket.java:473)       *
    *                       at com.rocketsoft.net.                 *
    *                      RC4ServerSocket.accept(RC4ServerSocket. *
    *                      java: 43) at                            *
    *                      sun.rmi.transport.tcp.                  *
    *                      TCPTransport$AcceptLoop.                *
    *                      executeAcceptLoop(TCPTransport.         *
    *                      java:381) at sun.rmi.transport.tcp.     *
    *                      TCPTransport$AcceptLoop.                *
    *                      run(TCPTransport.java:353)              *
    *                      at java.lang.Thread.run(Thread.java:    *
    *                      736)                                    *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49224

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-22

  • Closed date

    2016-03-15

  • Last modified date

    2016-04-05

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

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

    UI36220

Modules/Macros

  •    CQMBLOB  CQMCAEPT CQMJAR   CQMSSV   CQMSWD
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R320 PSY UI36220

       UP16/03/18 P F603

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0"}]

Document Information

Modified date:
31 March 2021