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 Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Dec 4, 2023

RELATED IDEAS

Detection of long running API calls in CHIN

When a MQget call drives a pageset scan the MQI call seems to never end. The reason is that the pageset is receiving updates at a high pace. The UOW associated can remain in MQ for more than 30 hours where it has a high I/O rate to the pageset. The UOW is very hard to detect. If it is a client-channel the CHIN will make sure the UOW continues even if the IP connection is dropped. In our case it was holding an exclusive OPEN to a queue on the pageset. Which made the service (QREP apply side (LUW)) unable to open the queue again. MQ must be able to detect when the situation persist for an abnormal long time and alert it. Being in a API call for hours is not correct behavior.

Secondly if the situation is found the only solution is to stop the task that has the UOW. In case of the CHIN task this would affect a lot of well behaving UOW as well. So the need for a method to abnormal end such a UOW is required. That could be in the form of a “Cancel conn” command or a WTOR when the MQI call has existed for more than a given time (the “max time” could be given with a parm somewhere).


Idea priority Medium
  • Admin
    Matthew Leming
    Reply
    |     Mar 18, 2024

    This is a valid requirement. However it doesn't fit with our delivery plans for the next year or so.
    As a result we are declining this idea. While declined the idea can still be voted, and commented, upon.

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.