IBM Support

IT13145: FTESTOPAGENT REPORTS TIMEOUT ERRORS, BUT AGENT ACTUALLY STOPS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An intermittent error is seen in IBM MQ MFT when running the
    fteStopAgent command where the command returns an error, but the
    MFT agent does  stop.
    
    Stdout contains
    BFGCL0467I: Issuing immediate stop request to agent 'QM1'. The
    command will wait for the agent to stop.
    followed by this message in stderr:
    BFGCL0464E: Failed to stop agent 'QM1'. Reason: BFGNV0103E:
    Failed to read message from socket. Reason: No such file or
    directory
    
    The fteStopAgent command gives RC=1 however the logs for the
    agent and process controller show that the agent does shut down
    in response to the stop request.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ V8 Managed File Transfer
    component who stop agents by issuing the fteStopAgent command on
    the same system as the agent is running on.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the fteStopAgent command is run on the same system as the
    agent, the command sends the stop request to the the agent's
    process controller, which forwards it on to the agent itself.
    When the agent has processed the request, it sends back a
    response to the command, via the process controller, indicating
    that it has stopped.
    
    There was a timing window in this processing which meant that
    the agent's process controller could stop before the
    fteStopAgent command had read the reply message.  If this
    happened, the fteStopAgent command would fail to read the
    message and report the following error:
    
    BFGCL0464E: Failed to stop agent 'QM1'. Reason: BFGNV0103E:
    Failed to read message from socket. Reason: No such file or
    directory
    

Problem conclusion

  • This timing issue has been resolved by adding logic to the
    fteStopAgent command which performs additional checks on the
    agent's status if no response message is seen.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.5
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT13145

  • Reported component name

    WMQ MFT V8.0

  • Reported component ID

    5724H7252

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-12

  • Closed date

    2016-04-29

  • Last modified date

    2016-05-03

  • 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

    WMQ MFT V8.0

  • Fixed component ID

    5724H7252

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 May 2016