IBM Support

PI74926: AGENTS HAVE INCORRECT STATUES OR EXPERIENCE CONNECTIVITY PROBLEMS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Agents can have incorrect statues or experience connectivity
    problems in UCD system with servers running in HA mode. Some
    examples or symptoms of these problems are:
    
    Agents can be in "Connecting" state when they should be online.
    The connection test always passes or passes intermittently.
    
    Agents can be in "Online" state but the connection test always
    fails or the agent is otherwise known to be not running or not
    connected. All steps run on the agent fail with the
    ackTimeout=true output property set.
    
    Agents can be in "Online" state but the connection test only
    passes intermittently and the agent is known to be running and
    connected. Steps run on the agent may sometimes fail with the
    ackTimeout=true output property set.
    
    A database deadlock is reported in the server log inside the
    class AgentTopologyTrackerForServer and is associated with an
    exception stack trace.
    
    An agent relay consumes 100% CPU and no agent connected to the
    relay responds to a connection test or can run a step.
    

Local fix

  • Two workarounds are known:
    1. Only run a single UCD server.
    2. Remove all agent relays.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Agents can have incorrect statues or experience connectivity *
    * problems in UCD system with servers running in HA mode. Some *
    * examples or symptoms of these problems are:                  *
    *                                                              *
    * Agents can be in "Connecting" state when they should be      *
    * online.                                                      *
    * The connection test always passes or passes intermittently.  *
    *                                                              *
    * Agents can be in "Online" state but the connection test      *
    * always                                                       *
    * fails or the agent is otherwise known to be not running or   *
    * not                                                          *
    * connected. All steps run on the agent fail with the          *
    * ackTimeout=true output property set.                         *
    *                                                              *
    * Agents can be in "Online" state but the connection test only *
    * passes intermittently and the agent is known to be running   *
    * and                                                          *
    * connected. Steps run on the agent may sometimes fail with    *
    * the                                                          *
    * ackTimeout=true output property set.                         *
    *                                                              *
    * A database deadlock is reported in the server log inside the *
    * class AgentTopologyTrackerForServer and is associated with   *
    * an                                                           *
    * exception stack trace.                                       *
    *                                                              *
    * An agent relay consumes 100% CPU and no agent connected to   *
    * the                                                          *
    * relay responds to a connection test or can run a step.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to UCD version 6.2.3.1                               *
    ****************************************************************
    

Problem conclusion

  • Fixed in UCD version 6.2.3.1
    

Temporary fix

  • Two workarounds are known:
    1. Only run a single UCD server.
    2. Remove all agent relays.
    

Comments

APAR Information

  • APAR number

    PI74926

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    621

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-13

  • Closed date

    2017-02-14

  • Last modified date

    2017-02-14

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

  • R623 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2021