Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Under review
Created by Guest
Created on Nov 7, 2025

Increase the robustness of RDQM failover when a node in the cluster is unhealthy. (Please refer to case number: TS020441085)

In certain situations, a system on which an RDQM node runs can become so unhealthy that it impacts that ability of the queue manager to fail over to another node. For example, this could be a system that runs at 100% CPU utilization for a sustained period and prevents failover operations from completing; while uncommon, if this situation does occur it impacts the availability of the queue manager. There should be a mechanism in RDQM to forcibly eject an unhealthy node from the cluster to allow the queue manager to start on one of the remaining nodes. This improvement would make RDQM more robust and capable of maintaining queue manager availability, even in scenarios where an unhealthy system affects the ability to fail over to another node.

Idea priority Urgent