IBM Support

IC68925: WMQFTE V7 PROTOCOL BRIDGE AGENT STARTS TO LOG BFGIO0134E FOR EVERY SCHEDULED TRANSFER AND TRANSFERS DO NOT GET SENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a WebSphere MQ File Transfer Edition (WMQFTE) v7 bridge
    agent transfer is canceled, the bridge resource is not
    recovered. After about 50 canceled bridge transfers
    the protocol bridge agent starts to create an FFDC log file
    with message BFGIO0134E, for every scheduled transfer, and
    continues to do so until it is stopped. Any new files that
    appear after that point are not transferred until the bridge
    agent is restarted.
    The BFGIO0134E FFDC log file shows:
    Cause:      com.ibm.wmqfte.io.FTETransferIOException:
    BFGIO0134E: An   internal error has occurred. There are no
    available bridge sessions to process transfer 12345...
    ADDITIONAL KEYWORDS: WMQ FTE scheduled transfers
    

Local fix

  • Restart the WMQFTE bridge agent using fteStartAgent
    

Problem summary

  • A protocol Bridge agent leaks FTP containers in certain
    circumstances, such as a nuber of transfers being cancelled:
    This results in an FFDC being generated with the following
    information:
    
    Cause:      com.ibm.wmqfte.io.FTETransferIOException:
    BFGIO0134E: An
    internal error has occurred. There are no available bridge
    sessions to
    process
    transfer 414d5120514d544147303120202020204271f64b20725adf.
    com.ibm.wmqfte.io.FTETransferIOException: BFGIO0134E: An
    internal error
    has occurred. There are no available bridge sessions to process
    transfer
    414d5120514d544147303120202020204271f64b20725adf.
    
    USERS AFFECTED:
    Those using the Protocol Bridge
    
    PLATFORMS AFFECTED:
    All Supported
    

Problem conclusion

  • CONCLUSION:
    A WMQFTE transfer which has one (or both) ends is a bridge agent
    is allocated a bridge container to handle all transactions with
    the protocol file server. These containers are returned to the
    pool on completion of the transfer. However, if the transfer was
    cancelled or had failed (for example remote end disappeared)
    then the transfer would have been terminated, but the container
    was not returned to the pool. Once all the containers have been
    used up (~50) future transfers will be rejected with reason code
    "BFGIO0134_NO_SESSIONS".
    

Temporary fix

  • An iFix is available on request
    

Comments

APAR Information

  • APAR number

    IC68925

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-31

  • Closed date

    2010-06-22

  • Last modified date

    2010-06-22

  • 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 FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R702 PSY

       UP

  • R700 PSN

       UP

  • R701 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 June 2010