IBM Support

IT34623: Managed File Transfer agent abends after migrating from version 8.0.0.3 or earlier.

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 IBM MQ 8.0.0.0, 8.0.0.1, 8.0.0.2 or 8.0.0.3 Managed File
    Transfer agent, is migrated to a later version. After the
    migration, the agent fails to start and generates an ABEND file
    called:
    
      ABEND.FTE<.date_and_timestamp>.<number>.log
    
    in the
    <MQ_DATA_PATH>/mqft/config/<coordination_qmgr_name>/agents/<agen
    t_name>/ffdc directory containing the following information:
    
    ...
    Thread:     16 (RecoveryThread)
    Class:      com.ibm.wmqfte.thread.FTEThread
    ...
    Method:     uncaughtException
    Probe:      ABEND_001
    Cause:      java.lang.OutOfMemoryError: Java heap space
    java.lang.OutOfMemoryError: Java heap space
    	at
    com.ibm.wmqfte.statestore.impl.FTEStateUtils.getStringFromByteBu
    ffer()
    	at
    com.ibm.wmqfte.statestore.impl.FTEChecksumDataImpl.fromByteBuffe
    r()
    	at
    com.ibm.wmqfte.transfer.FileProcessorState$TransferItemState.fro
    mByteBuffer()
    	at
    com.ibm.wmqfte.transfer.FileProcessorState.fromByteBuffer()
    	at
    com.ibm.wmqfte.statestore.impl.FTECheckPointState.fromByteBuffer
    ()
    	at
    com.ibm.wmqfte.statestore.impl.FTEMutableCommonState.<init>()
    	at
    com.ibm.wmqfte.statestore.impl.FTEMutableSenderState.<init>()
    	at
    com.ibm.wmqfte.statestore.impl.FTEStateUtils.getStateFromBuffer(
    )
    	at
    com.ibm.wmqfte.statestore.impl.FTEStateUtils.getStateFromMessage
    ()
    	at
    com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence.recover(
    )
    	at
    com.ibm.wmqfte.statestore.impl.FTEStateStoreImpl.recover()
    	at
    com.ibm.wmqfte.agent.AgentRecoveryRunnable.recoverStateStore()
    	at com.ibm.wmqfte.agent.AgentRecoveryRunnable.run()
    	at java.lang.Thread.run()
    	at com.ibm.wmqfte.thread.FTEThread.run()
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of IBM MQ Managed File Transfer,
    who have agents that:
    
    - Have been migrated from IBM MQ versions 8.0.0.0, 8.0.0.1,
    8.0.0.2 or 8.0.0.3 of the Managed File Transfer component.
    - And have in-flight managed transfers at the time the migration
    takes place (ie. the system queue SYSTEM.FTE.STATE.<agent_name>
    for the agent contains at least one message).
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    IBM MQ Managed File Transfer agents store information about
    in-flight managed transfers in messages that are held on the
    SYSTEM.FTE.STATE.<agent_name> queue. There is one message on the
    queue for each managed transfer that an agent is currently
    participating in.
    
    APAR IT03450 changed the format of the messages on the
    SYSTEM.FTE.STATE.<agent_name> queue, so that they contained some
    extra information relating to the "fail transfer on first
    failure" functionality added as part of that APAR. APAR IT03450
    was included in the following MQ Fix Packs:
    
    - WebSphere MQ 7.5.0.6 (and later).
    - IBM MQ 8.0.0.4 (and later).
    
    and shipped as part of the MQ 9.x GA releases.
    
    The changes to the format of the messages on the
    SYSTEM.FTE.STATE.<agent_name> queue meant that:
    
    - If an agent was using either the WebSphere MQ 7.5.0.5 (or
    earlier) Managed File Transfer component, or the IBM MQ 8.0.0.3
    (or earlier) Managed File Transfer component.
    - And the agent still had in-flight managed transfers in
    progress at the time that it was stopped and migrated to a newer
    release.
    
    then, when the agent restarted, it would incorrectly process the
    messages on the queue, as it was expecting them to contain data
    that was not present. This would result in the agent generating
    an ABEND file and shutting itself down.
    
    APAR IT17550 was originally raised to resolve this. However, due
    to a logic issue, the fix for that APAR did not work correctly
    if the agent was updated from IBM MQ versions 8.0.0.0, 8.0.0.1,
    8.0.0.2 or 8.0.0.3 of the Managed File Transfer component. As a
    result, agents migrated from those versions of the component
    would still fail to parse the messages on the
    SYSTEM.FTE.STATE.<agent_name> queue, generate an ABEND file and
    shut themselves down after they had been migrated.
    

Problem conclusion

  • The logic that was originally added to Managed File Transfer
    agents as part of APAR IT17550 has been modified to ensure that
    it works correctly in all situations. This means that:
    
    - If an agent is migrated from IBM MQ versions 8.0.0.0, 8.0.0.1,
    8.0.0.2 or 8.0.0.3 of the Managed File Transfer component
    - And the agent was involved in some in-flight managed transfers
    when it was migrated,
    
    then the agent will successfully process the messages for those
    managed transfers from its SYSTEM.FTE.STATE.<agent_name> queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.8
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.2
    
    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

    IT34623

  • Reported component name

    IBM MQ MFT V9.1

  • Reported component ID

    5724H7272

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-21

  • Closed date

    2020-11-20

  • Last modified date

    2020-11-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

    IBM MQ MFT V9.1

  • Fixed component ID

    5724H7272

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
21 November 2020