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 DataPower Gateway
Created by Guest
Created on Aug 24, 2022

Add a "Maximum persistent reuse" parameter for the backside of an MPGW or WSP

On an MPGW or a WSP, I want to be able to configure that the persistent backside connection should be closed after X amount of requests have been sent through that connection. I can already do this for the frontside by setting the "Maximum persistent reuse" setting in the HTTP(S) listener. But when a connection is closed by the server, it introduces sporadic errors due to the race condition described here:

So to avoid the race condition, it should be the client instead of the server that closes the connection. For this we will need the "Maximum persistent reuse" option added for backside persistent connections.

The reason we want all TCP connections to be closed after X amount of reuses is to allow graceful shutdown of backend connections. If the client (in this case DataPower) keeps the TCP connection open, then the server cannot gracefully shutdown the HTTP(S) service without introducing the race conditon mentioned earlier.

Idea priority High
  • Guest
    Jul 7, 2023

    I want this on the backside of the API GW too.