IBM Support

IC66063: WMQ FTE 702 HAS A TIMING ISSUE THAT OCCURS WHEN NEGOTIATION BETWEEN 2 AGENTS ARE TAKING LONGER THAN NORMAL TO COMPLETE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When problems occur in the TCP/IP networking environment the
    WMQFTE agent may appear as if it is hung. In actuality, the
    problem occurs because the MQ Channel is attempting to reconnect
    to its queue manager. A timing issue in the code occurs when the
    negotiation between 2 agents is taking too long.
    

Local fix

  • On any agent that is acting as the source of a transfer, set
    maxTransferNegotiationTime=300000 in the agent.properties file.
    This increases the timeout to wait for the negotiation message
    from the other agent in the transfer from 30s to 5m.
    

Problem summary

  • This problem can occur when a transfer is in a resynchronising
    state due to the initial negotiation timing out and a
    notification is received from the destination while the sender
    is processing the command response message. The exception is
    thrown because the processsing of the command message has read
    the state from the persistent store under syncPoint which has
    not yet been committed when then notification is received.
    
    USERS AFFECTED:
    Those with slow or unreliable networks
    
    PLATFORMS AFFECTED:
    All
    

Problem conclusion

  • The FTEStateStoreImpl notifyAcknowledgement method has been
    updated to ignore WMQApiFailureExceptions if the reason code is
    MQRC_NO_MSG_AVAILABLE
    

Temporary fix

  • No iFix available - Fixed in fixpack 7.0.2.1
    

Comments

APAR Information

  • APAR number

    IC66063

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-03

  • Closed date

    2010-02-23

  • Last modified date

    2010-02-23

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

Document Information

Modified date:
23 February 2010