IBM Support

PI84420: MISLEADING ERROR MESSAGES IN LOGS WHEN CAE SERVER V3.3 CONNECTS TO CAE AGENT V3.2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When CAE Server starts, it always tries to send EO request to
    CAE Agent. Server should not send EO request to CAE Agent v3.2.
    We see following messages
    .
    [11:43:37.911]  WARNING: Read
    timed out
    java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at
    java.net.SocketInputStream.socketRead(SocketInputStream.java:127
    )
     at java.net.SocketInputStream.read(SocketInputStream.java:181)
     at java.net.SocketInputStream.read(SocketInputStream.java:152)
    .
    During Alerts monitoring when no Alerts come to CAE Server
    following message may be printed in agent log
    .
    06.25.15 STC41523 CQMC0106E BAD PROTOCOL VERSION. EXPECTED 5,
    RECEIVED 4 ON SOCKET 5.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Query Monitor z/OS.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Scenario:                               *
    *                      # Point CAE Agent 1 to connect to CAE   *
    *                      Server 1 using IPAddress1 with          *
    *                      ListenerPort1                           *
    *                      # Stop this CAE Agent 1 and re-map to   *
    *                      another CAE Server 2 with the same      *
    *                      ListenerPort1                           *
    *                      # Create new CAE Agent 2 for CAE        *
    *                      Server 1 and connect using              *
    *                      IPAddress2 with another ListenerPort2   *
    *                      Even though new CAE Agent 2 is          *
    *                      connected to CAE Server 1, CAE          *
    *                      Server 1 will use                       *
    *                      IPAddress1:ListenerPort1 for            *
    *                      connection with CAE Agent.              *
    *                                                              *
    *                      When CAE Server starts, it always       *
    *                      tries to send EO request to CAE Agent.  *
    *                      Server should not send EO request to    *
    *                      CAE Agent v3.2. We see following        *
    *                      messages                                *
    *                       11:43:37.911   WARNING: Read           *
    *                      timed out                               *
    *                      java.net.SocketTimeoutException: Read   *
    *                      timed out at java.net.SocketInputStre   *
    *                      am.socketRead0(Native Method)  at       *
    *                      java.net.SocketInputStream.socketRea    *
    *                      d(SocketInputStream.java:127)           *
    *                      at java.net.SocketInputStream.rea       *
    *                      d(SocketInputStream.java:181)           *
    *                      at java.net.SocketInputStream.read(So   *
    *                      cketInputStream.java:152)               *
    *                      During Alerts monitoring when no        *
    *                      Alerts come to CAE Server following     *
    *                      message may be printed in agent log     *
    *                      06.25.15 STC41523 CQMC0106E BAD         *
    *                      PROTOCOL VERSION. EXPECTED 5,           *
    *                      RECEIVED 4 ON SOCKET 5.                 *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI84420

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    330

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-12

  • Closed date

    2017-08-28

  • Last modified date

    2017-10-02

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

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

Modules/Macros

  • CQMEO
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R330 PSY UI49877

       UP17/09/11 P F709

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
06 November 2021