IBM Support

IT08922: MQMFT V7.5 A NOSIZECHANGE RESOURCE MONITOR TRIGGERS ON A FILE LOCKED BY AN EXTERNAL PROCESS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A WebSphere MQ Managed File Transfer (MFT) directory resource
    monitor, configured with a "noSizeChange" trigger condition,
    triggers when the file is locked by an external process. If the
    directory resource monitor is configured to submit a managed
    transfer request for this file, then the agent will fail to
    transfer it and will report the error:
    
      BFGIO0082E: A file open for read failed due to a Java
    IOException with message text <path_to_file> (The process cannot
    access the file because it is being used by another process.)
    
    in the transfer log progress message.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of WebSphere MQ Managed File
    Transfer who use a directory resource monitor, configured with a
    "noSizeChange" trigger condition, that then submits a managed
    transfer request for the same file that caused the resource
    monitor to trigger.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A WebSphere MQ Managed File Transfer (MFT) directory resource
    monitor polls a directory to search for files matching a
    configured pattern. When a suitable file is detected, the
    directory resource monitor triggers an event, typically this is
    sending a managed transfer request to the agent.
    
    If a WebSphere MQ MFT directory resource monitor is configured
    to use either a "match" or "fileSize>=<size>" trigger condition,
    then even if a detected file matches the trigger condition, a
    trigger event is not fired if the file detected is deemed to be
    locked by an external process or application. However, if the
    directory resource monitor was configured to use the
    "noSizeChange" trigger condition, then a trigger event would
    occur regardless of whether the detected file is locked by an
    external process or not.
    

Problem conclusion

  • This APAR changes the WebSphere MQ Managed File Transfer
    directory resource monitor code for the "noSizeChange" trigger
    condition such that a trigger event does not occur in the case
    where a file is detected that matches the trigger criteria but
    that file is determined to be locked by an external process.
    
    If a file is locked, such that the directory resource monitor
    cannot access it and determine its size, then the counter for
    the number of times the directory resource monitor detects its
    size as being unchanged begins when the file becomes unlocked.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.6
    v7.5       7.5.0.6
    v8.0       8.0.0.4
    
    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

    IT08922

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-14

  • Closed date

    2015-05-29

  • Last modified date

    2016-05-06

  • 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

  • Fixed component ID

    5724H7242

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCUHLE","label":"WMQ Managed File Transfer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 May 2016