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 Submitted
Workspace webMethods API Gateway
Created by Guest
Created on Nov 5, 2024

RELATED IDEAS

Expand connection timeout configuration to include time spent waiting for JSSESecureSocketFactory

From our support ticket, “watt.security.ssl.resumeClientSessions default value is "false" and if it is set to true, JSSESecureSocketFactory object is reused while creating the socket. Since it is reused and synchronized, it blocks until the socket is created.”

watt.security.ssl.resumeClientSessions configuration is used for reusing the SSL/TLS session to reduce overhead for repeated calls to the same address. However, if connection is not successful, the shared nature of this session object will cause the connection timeout for each of the API calls to stack up.

For example, if connection timeout is set to 30 seconds, 10 calls will cause the 10th call to wait for 300 seconds before connection timeout is thrown. During which, the thread will be stuck in a blocked state. In our production environment, this has caused some API calls to timeout after 1 hour instead of the configured value.

This means we essentially has to choose between a lowered overall throughput or a potential hogging thread issue if a connection issue occurred in a high traffic environment.

To resolve this, we would like API Gateway to expand the connection timeout configuration to include the time taken when waiting for the shared session.

Idea priority Urgent

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.