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 Nov 12, 2013

JMS Exception Listener is not notified if SHRCONV greater than 0

In a JMS application coded for asynchronous delivery of messages I have set an ExceptionListener to be notified of any error (e.g. input queue
GET_INHIBITED). If SHRCONV is set to >0 (using the new JMS model), the OnException method of the ExceptionListener is never called for errors like GET_INHIBITED.
Reverting to old JMS model (SHRCONV = 0) exhibits the required behaviour.

Idea priority High
RFE ID 41544
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
    Sep 11, 2014

    It is planned to release a modification to the behaviour in a future V8 fixpack. However you will have to actively "opt into" this behaviour, in order to maintain JMS specification compliance in the default configuration.