Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Dec 14, 2023

Avoid completing the reallocation process in case all sender channels are not running, to decrease CPU consumption

Refer to Case TS014865530 - High CPU consumption during MQ Message Reallocation

As per explanations in the Case,  the cluster message reallocation process is made of 2 steps that scans the transmission queue: the first one checks whether there are messages eligible to be reallocated and the second one to actually move the messages that are allowed to be re-routed. 

This process needs a lot of CPU. 

In case all the cluster sender channels to the remote queue managers are in Retry because the remote queue managers are down, all the 2nd pass through all of the messages is totally useless and consumes a lot of CPU for nothing. Before starting the 2nd pass (or any related heavy process), MQ should be sure that there is a suitable active channel to use to complete the reallocation process.

Idea priority Urgent
  • Admin
    Matthew Leming
    Mar 18, 2024

    At the moment I am afraid we have no plans to change how the cluster message reallocation processing works.
    As a result we are declining this idea. While declined the idea can still be voted, and commented, upon.