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 Mar 6, 2025

Provide the ability to pace external Get requests coming into a qmgr by slowing down channels or queues internally throttling the Getters

We have had a couple of issues where the volume of external Get requests have caused concern. One such issue was when we wanted to control how fast a Getter application could consume messages off a queue, the reason being is that consuming messages via a SVRCONN is relatively expensive CPU wise and we would like to control the peak CPU consumption as this may be impactful to other applications. Another issue was where we have had disruptive Getter applications causing issues by hitting capacity limits within the qmgr.  Maybe something similar to Kakfa topic publish/consume quotas could be implemented within a qmgr for channels and queues ?             

Idea priority High