IBM Support

IT37958: Wrong error reported if managed transfer fails during initialization due to "SocketException: Connection reset"

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When an MQ Managed File Transfer protocol bridge agent is
    connecting to a file server using the SFTP protocol, and is
    acting as the source agent for managed transfers, if the agent
    encounters an unexpected issue when trying to connect to the
    file server while trying to resolve the list of transfer items
    for a managed transfer, the managed transfer fails with the
    incorrect supplementary message:
    
    BFGIO0110E File "<FileName>" does not exist
    
    Some examples of the connectivity issues that can cause this
    are:
    
    -SocketException: Connection reset
    -SocketTimeoutException: Read timed out
    -connect, Auth fail
    -createSocket, timeout
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ 9.2 Managed File Transfer
    (MFT) who have protocol bridge agents (PBAs) that:
    
    - Connect to a file server using the SFTP protocol.
    - And act as the source agent for managed transfers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If an MQ Managed File Transfer (MFT) protocol bridge agent (PBA)
    was:
    
    - Configured to connect to a file server using the SFTP
    protocol.
    - And encountered an unexpected connectivity issue when
    connecting to that file server in order to resolve the list of
    source items to include in a managed transfer request.
    
    then the managed transfer would be marked as "Failed", which was
    expected. However, due to an issue with the way the failure was
    processed, the wrong supplementary message:
    
      BFGIO0110E File "<FileName>" does not exist
    
    was reported for the managed transfer.
    
    Some examples of unexpected connectivity issues when connecting
    to a file server using the SFTP protocol are shown below:
    
    -SocketException: Connection reset
    -SocketTimeoutException: Read timed out
    

Problem conclusion

  • MQ Managed File Transfer protocol bridge agents (PBAs) have been
    updated so that if an unexpected connection issue occurs while
    trying to resolve the list of source files to include in a
    managed transfer, the managed transfer will fail with the
    supplementary message:
    
      BFGRP0038I: The file transfer request failed due to :
    <exception>
    
    which describes the cause of failure.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.5
    
    The latest available 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

    IT37958

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-08-10

  • Closed date

    2021-11-08

  • Last modified date

    2021-11-08

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
09 November 2021