IBM Support

PM28732: Error Connection to agent timed out with use of .monitor

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Project build step that users .monitor command will failed with
    'Connection to agent timed out.' if step runs longer than
    console 'Agent Connect Timeout' setting.
    
    Steps to reproduce:
    
    - Create project with step to run .monitor command on file.
    
    ie:
    .monitor -w 2 /tmp/test
    
    - Run said project.
    
    Expected result:
    
    Project step continue to run until file being monitored changed
    file size to continue step execution.
    
    Actual result:
    
    Project step failed after console 'Agent Connect Timeout' is
    exceeded.
    
    Workaround:
    
    Increase 'Agent Connect Timeout' setting to allow the .monitor
    command to complete.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The engine was using the agent connection timeout was used
    to judge how frequently heartbeats were expected to be
    received by the engine.  Agents will heartbeat every 15
    seconds by default regardless of this setting, so it did not
    make sense to use it for this purpose.
    

Problem conclusion

  • Although originally noticed in relation to .monitor, this is
    not unique to that command.  Any long-running step command
    would have been subject to this restriction.  The connection
    timeout will now only be used in connection with the
    heartbeat if it is at least 20 seconds; otherwise 20 seconds
    will be used, instead.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM28732

  • Reported component name

    BUILD FORGE EE

  • Reported component ID

    5724S2701

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-12

  • Closed date

    2011-08-31

  • Last modified date

    2011-08-31

  • 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

    BUILD FORGE EE

  • Fixed component ID

    5724S2701

Applicable component levels

  • R711 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSB2MV","label":"Rational Build Forge"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 August 2011