Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Not under consideration
Workspace webMethods API Gateway
Created by Guest
Created on Jun 1, 2025

RELATED IDEAS

Add Reconnect and Retry Configuration Properties to Ignite Cluster in webMethods API Gateway

In the current implementation of webMethods API Gateway, Ignite is used to support clustering functionality. However, the Ignite component lacks built-in configuration properties to automatically attempt reconnection or perform retries in the event of temporary network interruptions (e.g., 5–10 minutes of downtime).

This limitation means that even minor and recoverable network disturbances can cause cluster disconnection, and the cluster does not self-heal without manual intervention. Currently, the only way to re-establish the connection after such interruptions is to restart the API Gateway nodes.

We request the addition of configurable properties such as:

  • Maximum number of retry attempts
  • Retry interval duration
  • Total retry timeout duration

This would allow Ignite to automatically recover from transient network failures without requiring a full restart of the API Gateway.

Idea priority High
  • Admin
    Sivaraj Lenin
    Sep 2, 2025

    Thank you for submitting your enhancement request regarding reconnect and retry configuration properties for the Ignite Cluster in webMethods API Gateway.

    After careful evaluation, we've decided to mark this request as "Not under consideration" for our product roadmap. While we understand the potential value of this feature, in containerized environments, health checks automatically restart API Gateway containers that become disconnected from the cluster, effectively providing the self-healing capability without manual intervention. Given this existing solution and limited demand from our broader customer base, we haven't prioritized implementing additional reconnect and retry properties.

    We appreciate your continued engagement and encourage you to share any future enhancement ideas you may have.

    Best regards,

    Sivaraj Lenin

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.