Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 Functionality already exists
Categories Other
Created by Guest
Created on Jun 4, 2024

SFG Resiliency

There are 2 RFEs related.

This is the 2nd.

The first is SFG-I-325


Customer was processing a high volume of transactions via filegateway when their environment experienced a network issue.
Node 1 had its communication impacted with node 2. Communication was not unavailable, but extremely slow.
The network problem was that node 1 had its network latency between the server and any other end (switch, database and node 2) increased to above 5 seconds.

Focuses on why would any sort of problem with node 1 result in a crash of Node 2.

Node 2 had difficulty communicating with node 1. Node 2 had difficulty communicating with node 1 and the database, thus processing processing was impacted.

When there is a difficulty in communication between the nodes and/or when there is a significant increase in latency between the ends (nodes, database, etc.), the nodes must enter a treatment state so that if a node goes down, it does not impact the next one node.
Or, if the next node has difficulty communicating with the degrading node, go into "emergency" mode to reduce or nullify the impact on other nodes.

  • Admin
    Mark Allen
    Jul 3, 2024

    Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

    Our development and L3 teams have looked into your case. We believe that there needs to be a full root cause analysis done about your situation. Support has provided a list of recommendations and are waiting to hear back from you. The report highlights significant DB health issues that need to be addressed to avoid a situation like this again. Our recommendation is to open a support case, focused on DB tuning and configuration guidance for slower networks.

    Another recommendation we can provide is to use the JDBC pooling feature in 6.2.0.x to help with refreshing DB pool connections, but if the network is having fundamental issues, the refreshed DB connections will still continue to fail until this is addressed. You could increase the timeout settings, but that would not be a robust and permanent solution.

    There is no product enhancements identified in this case yet, so I'm going to close this RFE as "Functionality already exists". Again, we suggest a new support case to understand the root cause of this outage.

  • Guest
    Jun 7, 2024

    Hello, I'm the customer IT Manager that are responsible for that tech product here in the company. 

    That Issue has occurred on February 26th 2024. During the war room activities we've opened IBM Tickes:  TS015557799 and TS015560294, where We've upladed all the logs and detalis that you can analyze.

    Please contact and keep post Bruno Neuberger Leda (IT Specialist IBM Sterling B2B - Expert Labs / Sustainability Software). He has all the historical details about that issue.



    Roberto Harada

    IT Manager At Itaú-Unibanco

  • Admin
    Mark Allen
    Jun 5, 2024

    Thank you for taking the time to provide your ideas to IBM. I truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations and ideas.

    I need a little more information to understand your idea:

    Expected behaviour for B2Bi/SFG is seamless failover when configured appropriately. If you are encountering a situation where it is not failing over when there are communication failures then we need additional information from logs to understand your specific scenario.

    Thank you for taking the time to provide your idea to IBM. Given the duration of time that has elapsed for this issue, would you please confirm if this idea remains relevant? It will be helpful to confirm with an updated description of the problem so that we have a clear picture of the request. We look forward to your response.