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
Workspace App Connect
Created by Guest
Created on Jul 1, 2014

Eliminate rollback delay in Message Broker

Message Broker currently has a built-in delay of 1 second on the message rollback path. As per the referenced PMR, this delay is the mechanism used to allow time for internal object reset and to prevent processor swamping in case of message loops. I have the following request related to this:

1. Instead of depending on a timer or delay for resetting of internal state, broker should actively monitor such state and complete the rollback activity as soon as feasible.

2. For preventing processor and log saturation, it may be useful to have a delay in the requeue path. However it should be configurable, at least in the following ways:

a. Allow the delay duration to be configurable.
b. Allow specifying the message backout count after which the delay kicks in

This will allow the product users to determine appropriate parameters based on experienced resource usage and throughput.

Additionally I would like a discussion of this topic to be available in broker documentation. Currently this information is not documented, which can lead clients to depend on broker's rollback mechanism without realizing they are incurring a delay per failed message.

Idea priority Medium
RFE ID 55561
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Aug 5, 2014

    Thanks for raising. A rather advanced configuration option, but one that could provide utility for some customers nonetheless! We'll look at adding this to a future release.