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.


Add a new idea Subscribe
Status Future consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Jan 13, 2020

RELATED IDEAS

MQ Resilience

Related to CASE TS003034554


1) Allow for a parameter on the queue manager object to set max number of dynamic queues. (like we have with channels in the CHIN) This would have made the rogue application and other applications unable to continue creating dynamic queues, but it would have saved the queue manager. Or even better detect the storage usage and fail queue creation when it is at a critical level. Also allow for storage needed by CMDSERV to actually display the exsiting queues.
2) MQ itself must dis-allow the creation of new object, when it detects low on local storage. MQ needs to keep enough available local storage to give response to display commands. A version of this could be that gives an error message if output is too great to handle – instead of crashing.
3) Allow MQ to be started in a “light” version for debugging purposes. One of the problems we had was, when we started the queue manager, all sort of jobs and tasks would be waiting and start putting their work into MQ, which then would crash again. It would helpful with a handle to stop all workload and only allow a few privileged users to work with the MQ.

Idea priority Medium
RFE ID 139378
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |     Apr 22, 2020

    This is something that we would like to look at for a future release of MQ

  • Guest
    Reply
    |     Jan 21, 2020

    It is a must have feature that the QueueManager can't be crashed by a rogue application. Of course, many circumstances will stop the qmgr from working (full log space, full queue space, paused channels, ...) but all of this shouldn't crash the system with a large recovery time to rebuild everything.
    Everything that helped the qmgr to stay healthy is strongly recommended.

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.