Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Feb 13, 2013

Allow queue-high and queue-low events to be reset when messages have expired and the MQGET call returns no messages

When messages go to an MQ queue that eventually causes the Queue Depth High Event to be triggered, this enables the Queue Depth Low Event (as expected). These messages might then expire and will eventually be deleted once the queue is browsed. Currently when this happens, the Queue Depth Low Event never gets triggered and, as a result, the Queue Depth High Event never gets enabled.

IBM suggests that this is working as expected. “If an MQGET call completes with MQRC_NO_MSG_AVAILABLE and expired messages on the queue are processed along the way, event messages are not generated and the high/low depth threshold switches are not flipped.” It seems that the queue-high and queue-low thresholds would be reset only following a ‘successful' MQGET call and that, when no messages are returned because they've all expired, this does not class as a successful MQGET call. However, from a logical viewpoint, if messages have expiry set and by the time the MQGET call is issued they've expired, then this would appear to be MQ working as expected and thus it would not be unreasonable to expect the thresholds to be reset in these circumstances.

So, once the queue-high alert has been triggered due to a high-queue depth, this request is to allow the Queue-High event to be re-enabled and the Queue-Low event to be disabled automatically when the queue depth drops from above to below the queue-low threshold as a result of an MQGET call returning no messages due to messages having expiry set and where the time set has expired (which, as such, is not really an 'error' as this a perfectly normal outcome following an MQGET call).

Idea priority Medium
RFE ID 31226
RFE Product IBM MQ
  • Guest
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Jun 2, 2015

    We will consider this for a future update to MQ as we do understand the inconsistency here.