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 Not under consideration
Created by Guest
Created on Aug 16, 2012

No reason returned when an attempt to commit a transaction in async put mode fails

When an WebSphere MQ classes for JMS application uses the WebSphere MQ asynchronous put functionality to send a message to a queue inside a transaction, and a failure occurs when putting the message (because the queue is full, for example), the attempt to commit the transaction will fail and an exception will be returned to the application. However, the exception does not contain any information about why the commit operation failed.

The exception should contain details about the reason why the transaction could not be committed (in this case, because of an asynchronous put failure), to help users understand what has caused the problem.

This information should be returned to the application in all transactional situations:

When the application is running in a "local" transaction.
When the application is participating in an XA transaction.
When the application is participating in a transaction controlled by RRS.

Idea priority High
RFE ID 25590
RFE Product IBM MQ
  • Guest
    Jan 7, 2022

    We recognise that this is a valid requirement. However it doesn't fit with our delivery plans for the next couple of years.

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

  • 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
    Oct 31, 2012

    We will consider this for a future version of MQ. However there are potential limitations/implications. For example, having additional information might be restricted to Java interfaces only, and not other languages. And it might not be feasible in XA transacted environments because the standard limits the type of information that can be returned. We will investigate deeper into these potential limitations if/when this gets put into a release plan.

  • Guest
    Aug 16, 2012

    This RFE is linked to WebSphere Application Server RFE 20110, which can be found at the URI shown below: