IBM Support

IT06296: WMQ-MFT 7.5: BFGUT0002E IS REPORTED AND PROBEID FFDC_010 OCCURS DURING FILE TRANSFER RECOVERY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Transfer has cancelled by source agent, then source agent
    reported an error:
    
    BFGUT0002E: An internal error has occurred. Product failure
    data was captured in file.
    
    In FDC files:
    *****************************
    Level: f750-FP-20130619-1001
    Time: 20/11/2014 07:49:05:970 JST
    Thread: 22 (CommandHandler)
    Class: com.ibm.wmqfte.statestore.impl.FTEStateStoreImpl
    Instance: 19331933
    Method: processRecoveryMessage
    Probe: FFDC_010
    Cause: null
    java.lang.Exception: Call stack
     at
    com.ibm.wmqfte.ras.impl.IncidentStream.(IncidentStream.jav
    a:219)
     at
    com.ibm.wmqfte.ras.impl.FFDCImpl.createIncidentStream(FFDCImpl.j
    ava:134)
     at com.ibm.wmqfte.ras.impl.FFDCImpl.ffdc(FFDCImpl.java:104)
     at
    com.ibm.wmqfte.ras.impl.FFDCImpl.internalCapture(FFDCImpl.java:7
    5)
     at com.ibm.wmqfte.ras.FFDC.capture(FFDC.java:208)
     at
    com.ibm.wmqfte.statestore.impl.FTEStateStoreImpl.processRecovery
    Message(FTEStateStoreImpl.java:1974)
    ......................
    
    You may also observe FDC shows "Transfer States:
    CancelledInProgressTransfer"
    ************************
    
    1) The transfer is in the recovery state.
    2) Destination side sent a re-synchronize message to the source
    to recover the transfer
    3) Before the source could handle this re-synchronize message,
    the transfer had been cancelled.
    4) This lead to the transfer being in the
    CancelledInProgressTransfer
    state.
    5) The re-synchronize message should have been discarded as
    there is no need to resync the transfer. In this case, an FDC
    was thrown.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of the WebSphere MQ V7.5 Managed
    File Transfer.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the following sequence of events occurred, a WebSphere MQ
    Managed File Transfer (MFT) agent that was acting as the source
    agent for a transfer, incorrectly generated an FDC file:
    
    1) A managed transfer had been initiated by WebSphere MQ MFT.
    
    2) The transfer encountered a recoverable error at the WebSphere
    MQ MFT destination agent.
    
    3) The transfer was then subsequently put into a "recovery"
    state.
    
    4) The destination agent sent a re-synchronize request message
    to the source agent to recover the transfer from a common
    checkpoint.
    
    5) Before the source agent actioned the re-synchronize message,
    the user requested the transfer to be cancelled (for example, by
    using the fteCancelTransfer command)
    
    6) While the source agent processed the cancellation request,
    the transfer was put into "Cancelling" state.
    
    7) Before this completed, the source agent then began to process
    the re-synchronize message (sent by the destination agent).
    
    8) As part of the processing of this, a check is made to ensure
    that the transfer is in a suitable state to be recovered.
    
    9) The source agent did not account for the "Cancelling" state
    and treated this as an error condition and so generated an FDC
    file.
    

Problem conclusion

  • The WebSphere MQ V7.5 Managed File Transfer agent code has been
    updated so that when a source agent receives a re-synchronize
    message for a transfer, this message is discarded when the
    transfer is already in the process of being cancelled by the
    source agent. Subsequently no FDC will be generated when this
    situation occurs.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.6
    
    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

    IT06296

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-04

  • Closed date

    2015-01-30

  • Last modified date

    2015-01-30

  • 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:
30 January 2015