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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Why this is useful:
Implementing a solution to automatically release the 'shmall' value after messages are processed in the queues is critical for seamless operations, especially in production environments where high availability and minimal downtime are essential.
Restarting the Queue Manager disrupts operations, causing unnecessary delays and potential impact on applications, which is not acceptable for businesses handling high-criticality workloads.
How it should work:
IBM MQ should include a mechanism to monitor and reclaim the allocated 'shmall' memory after queue processing is complete. The expected functionality from the customer end is that the memory is properly deallocated by the OS automatically after queue processing, without requiring a Queue Manager restart.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This is not something we plan to change in MQ. MQ tends to keep hold of allocated resources because it's more likely than not to need those resources again soon.
From development:
If the comes down to 'spikey' load causing deep queue build up at times, then you would in any case need to avoid overcommitting the shared memory on the system as a whole to be able to accommodate those spikes - so it's not clear that temporarily releasing MQ usage would actually be of much benefit to anyone.