IBM Support

IC82060: WEBSPHERE MQ FTE V7 AGENT PROCESS PRODUCES A DUPLICATE CONTAINER EXCEPTION, BFGBR0063E, FFDC WHEN IT RECEIVES A SOCKET ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ FTE agent produces an FFDC because socket
    exceptions are occuring when attempting to connect to an sftp
    server, this suggests that the Operating System the sftp server
    is on is running out of resources.   The FFDC has
    Start of FFDC
    *
    Filename:
    <drive:path>\logs\ffdc\FFDC.FTE.201203062229
    27374.359523848765437786.log
    Level:      f000-704-GM7-20110511-1307
    Time:       06/03/2012 22:29:27:374 SGT
    Thread:     <ThreadId>
    (TransferSender[<TransferId])
    Class:      com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl
    Method:     openTransfer
    Probe:      FFDC_002
    Cause:
    com.ibm.wmqfte.bridge.session.BridgeContainerException:
    BFGBR0063E: An internal error has occurred. Request for a
    duplicate
    container for transfer Id FTETransferReference
    [endPointType=SENDER,
    transferId=<TransferId>,
    wmqConnection=null] occurred when already present.
    com.ibm.wmqfte.bridge.session.BridgeContainerException:
    BFGBR0063E: An
    internal error has occurred. Request for a duplicate container
    for
    transfer Id FTETransferReference [endPointType=SENDER,
    transferId=<TransferId>,
    wmqConnection=null] occurred when already present.
     at
    com.ibm.wmqfte.bridge.session.BridgeSessionContainerManager.open
    Containe
    r(BridgeSessionContainerManager.java:87)
     at
    com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl.openTransfe
    r(Bridge
    FileFactoryHelperImpl.java:234)
     at
    com.ibm.wmqfte.io.FTEFileFactory.openTransfer(FTEFileFactory.jav
    a:651)
     at
    com.ibm.wmqfte.transfer.impl.TransferSenderRunnable.run(Transfer
    SenderRu
    nnable.java:366)
     at java.lang.Thread.run(Thread.java:736)
     at com.ibm.wmqfte.thread.FTEThread.run(FTEThread.java:64)
    Stack ids:
     com.ibm.wmqfte.transfer.impl.TransferSenderRunnable.$sccsid=@(#
    )
    com.ibm.wmqfte.agent/src/com/ibm/wmqfte/transfer/impl/TransferSe
    nderRunn
    able.java,jazz,f000,f000-704-GM7-20110511-1307 05/11/2011
    01:09:02 PM
    [05/11/2011 01:09:02 PM]
     com.ibm.wmqfte.thread.FTEThread.$sccsid=@(#)
    com.ibm.wmqfte.common/src/com/ibm/wmqfte/thread/FTEThread.java,j
    azz,f000
    ,f000-704-GM7-20110511-1307 05/11/2011 01:09:02 PM [05/11/2011
    01:09:02
    PM]
     com.ibm.wmqfte.io.FTEFileFactory.$sccsid=@(#)
    com.ibm.wmqfte.io/src/com/ibm/wmqfte/io/FTEFileFactory.java,jazz
    ,f000,f0
    00-704-GM7-20110511-1307 05/11/2011 01:09:02 PM [05/11/2011
    01:09:02 PM]
     com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl.$sccsid=@(
    #)
    com.ibm.wmqfte.io/src/com/ibm/wmqfte/io/bridge/BridgeFileFactory
    HelperIm
    pl.java,jazz,f000,f000-704-GM7-20110511-1307 05/11/2011 01:09:02
    PM
    [05/11/2011 01:09:02 PM]
    Arg[0]:     TransferId: FTETransferReference
    [endPointType=SENDER,
    transferId=<TransferId>,
    wmqConnection=null]  MQ USerId: <mquserId>
    Arg[1]:
    FFDC Extended Information
    ========================
    Agent Runtime
    -------------
        Start Time .......: Date and Time
        Last recovery Time: N/A
        Current Time......: Date and Time
        Product type......: SERVER
        Agent type .......: BRIDGE
    Active Source Tranfers
    ----------------------
        <TransferId> = ResumingTransfer
    *
    End of FFDC
    As a result of this the WebSphere MQ FTE recovery logic is
    driven. The
    customer sees that the transfer goes into recovery and when
    it tries to resume it can't get a connection to the sftp server.
    It
    appears that if it doesn't get a connection it leaves an open
    resource
    and when it retries the recover again you get the duplicate
    container
    exception (BFGBR0063E) and the resulting FFDC.
    

Local fix

Problem summary

  • During recovery of a transfer, a race condition existed in which
    a new sender thread could be created before the original sender
    thread has been properly disposed. This caused the BFGBR0063E
    error.
    
    USERS AFFECTED:
    All users of the protocol bridge
    
    PLATFORMS AFFECTED:
    All
    

Problem conclusion

  • The code has been altered to ensure that any new sender thread
    for a recovering transfer will wait for any old sender threads
    for that transfer to finish before attempting to restart the
    transfer. This ensures there's no conflict of multiple threads
    attempting to use the same resources for the same transfer.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 7.0.4.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC82060

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-15

  • Closed date

    2012-04-16

  • Last modified date

    2012-07-20

  • 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

  • R704 PSY

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

Document Information

Modified date:
20 July 2012