IBM Support

IT35258: Channels remain in initializing state for longer time while starting and message build up on SYSTEM.CHANNEL.INITQ

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

  • The sender/cluster sender channels stuck in initializing state
    while starting up.
    At times it takes a few minutes to start. The channel initiator
    appears to be
    taking a longer time to process messages from the
    SYSTEM.CHANNEL.INITQ and as such
    causing increase in queue depth.
    In addition, "AMQ9514E: Channel 'ChannelName' is in use." errors
    are reported in the
    queue manager error logs.
    

Local fix

  • A significant increase in the disconnect interval of the cluster
    receiver/receiver channels may help
    the respective remote end to run for a prolonged period of time.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    * All users of MQ distributed channels
    * Users using distributed channels configured with channel
    triggering and trigger type EVERY are likely to
       see this problem often.
    * Users using queue managers with several sender channels
    configured with channel triggering and cluster
       sender channels likely to be most affected by this problem.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in handling triggered channels caused the messages to
    be processed slowly resulting in slow channel startup and high
    queue depth in SYSTEM.CHANNEL.INITQ.
    

Problem conclusion

  • MQ code has been modified to resolve the problem in handling
    triggered MQ channels.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.10
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.3
    
    The latest available 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

    IT35258

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-11

  • Closed date

    2021-03-23

  • Last modified date

    2021-09-17

  • 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 BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

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

Document Information

Modified date:
18 September 2021