Skip to Main Content
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.


Status Submitted
Created by Guest
Created on Oct 15, 2025

API Gateway returns HTTP 500 instead of 502 on upstream socket reset at TCP level

We have an API exposed through a 3DNS URL configured in webMethods API Gateway 10.15 (routing policy).
The 3DNS resolves to two VIPs, each fronting two NGINX servers.

When one of the VIPs or one of the NGINX instances behind a VIP is shutdown abruptly, API Gateway encounters
a tcp socket-level connection reset error:

"Native service provider error. Reason : com.wm.app.b2b.server.ServiceException:
java.net.SocketException: Connection reset"

In such cases, API Gateway responds to the client with HTTP 500 Internal Server Error.

Expectation:
Since this is an upstream connectivity issue (not an internal API Gateway failure), the more appropriate
status code would be HTTP 502 Bad Gateway, indicating a backend communication problem.

Idea priority Low