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 Mar 31, 2015

HTTP Reply Nodes fail to recognise duplicate replies (SOAP Reply nodes do detect this)

When a HTTP timeout occurs using a broker-wide listener, the
processing thread continues to process resulting in an attempt to
submit a duplicate HTTP response message.

When using SOAP Nodes, this duplicate response attempt results in an
exception (as expected) - you cannot reply more than once using the
same reply identifier:

BIP3743 : An attempt was made to use a message
after it had timed out. The message was

However, when using HTTP nodes, the HTTP reply node fails to validate
whether the reply identifier has been consumed, you can actually place
a series of HTTP Reply nodes in a row and no exception occurs.

In this respect (unable to submit duplicate replies), HTTP Services and
SOAP Services (over HTTP) should behave in a consistent manner -
duplicate replies should not be possible, and the BIP codes returned -
in theory, could be identical when such an error occurs.

...or at least, HTTP nodes should return a BIP code that this specific to this error, much like the SOAP nodes do (when used over HTTP).

Idea priority High
RFE ID 68889
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Mar 11, 2021

    RFE Review. As part of our standard process for reviewing RFEs we have recently discussed this RFE and wish to note that it remains of long term interest to us. It is regrettable that we have not yet managed to prioritize this requirement for immediate action, but we will continue to monitor for popularity and keep it in mind for future plans. Status is maintained as Uncommitted Candidate.

  • 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