IBM Support

IT19530: BFGBR0062E error intermittently written to agent event log

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

  • An MQ V9.0.0.0 Managed File Transfer protocol bridge agent is
    acting as the source agent for managed transfers.
    Intermittently, the agent writes the following error into it's
    event log (output0.log):
    
    BFGBR0062E: An internal error has occurred. Request for session
    container for transfer Id FTETransferReference
    [endPointType=SENDER,
    transferId=414d512043514d524a3031202020202058b687e3215932f1,
    wmqConnection=com.ibm.wmqfte.wmqiface.WMQConnectionImpl@12196851
    60
    Queue Manager: CQMRJ01, randomDiscEventLogged: false,
    randomMqDiscForced: false, JmqiEnvironment:
    com.ibm.mq.jmqi.system.JmqiSystemEnvironment@7b454474, JmqiMQ:
    com.ibm.mq.ese.jmqi.ESEJMQI@3e47d578, Hconn: 0x7400019,
    bridgeFileServerProtocol=null] occurred when it is not present.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ V9 Managed File Transfer
    component who have protocol bridge agents that:
    
    - Act as the source agent for managed transfers.
    - Have been configured to use a ProtocolBridgeProperties.xml
    file that does not contain a <defaultServer> entry.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a protocol bridge agent is acting as a source agent for a
    managed transfer and receives a new managed transfer request, it
    performs some processing of that request to determine the
    transfer items that need to be included in the managed transfer.
    Once the list of transfer items has been created, the agent will
    start the managed transfer.
    
    If a transfer item contains a file path that is prefixed by a
    file server name, as shown below:
    
    server1:/home/user/file.txt
    
    then the protocol bridge agent will look in the
    ProtocolBridgeProperties.xml file for an entry for '"server1"
    and connect to that server. However, if a transfer item contains
    a file path that does not start with a file server name, like
    this:
    
    /home/user/file.txt
    
    the agent will assume that the item resides on the default file
    server, as defined by the <defaultServer> entry in the
    ProtocolBridgeProperties.xml file.
    
    If the transfer item did not start with a file server name, and
    the ProtocolBridgeProperties.xml file did not contain a
    <defaultServer> entry, then the agent would generate an invalid
    transfer item for the managed transfer. When the agent started
    processing the managed transfer, it was unable to determine
    which file server the transfer item was on. This caused the
    managed transfer to fail and the agent to report the following
    internal error in it's event log (output0.log):
    
    BFGBR0062E: An internal error has occurred. Request for session
    container for transfer Id FTETransferReference
    [endPointType=SENDER......bridgeFileServerProtocol=null]
    occurred when it is not present.
    

Problem conclusion

  • The MQ V9 Managed File Transfer component has been updated so
    that if a protocol bridge agent:
    
    - Receives a managed transfer request containing a transfer item
    that does not start with a file server name
    - And the ProtocolBridgeProperties.xml file for the agent does
    not contain a <defaultServer> entry.
    
    then the managed transfer is marked as "Failed" with the
    following error:
    
    BFGIO0410E: The protocol server name has not been specified, and
    no default protocol server has been defined for the protocol
    bridge.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    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

    IT19530

  • Reported component name

    IBM MQ MFT V9.0

  • Reported component ID

    5724H7262

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-03

  • Closed date

    2017-06-29

  • Last modified date

    2017-06-29

  • 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

    IBM MQ MFT V9.0

  • Fixed component ID

    5724H7262

Applicable component levels

  • R900 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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 June 2017