Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Apr 4, 2024

Config to limit Thread or Connection usage at API/URL level

We have had multiple high severity incidents where degradation of one service for reasons such as latency, looping, database contentions, deadlocks etc ends up quickly (in matter of seconds) exhausting all available threads within z/OS Connect thereby completely blocking traffic and flow on impacts. to provide better resilience, we are after a simple configuration in zConnect which could enforce limit on the number of threads/connections used by any single API by liberty and any excess requests for the endpoint should be immediately rejected with 5xx error.  We have numerous rate limits in the API management layer but they are unable to protect such issues and we believe there needs to be some level of defense and resilience in zConnect to prevent one service degradation impacting all other services.

Idea priority High
  • Guest
    Reply
    |
    May 1, 2024

    The recommendation would mean us as a customer needs to purchase, deploy and manage hundreds and hundreds of servers? We have hundreds of API's, so the recommendation would simply defeats the basics of resilient solutions and the value of such a complicated architecture. Not the response we expected for a critical resilience requirement and i don't understand for such a recommendation as opposed to implement a basic config for product to manage this.

  • Admin
    Demelza Farrer
    Reply
    |
    Apr 30, 2024

    This requirement has been evaluated. Looking at current plans, it is not likely that this would be implemented in future zOS Connect releases, so correspondingly
    this requirement is being rejected.

    It is recommended that isolating APIs in seperate servers to achieve this goal.

    You have an opportunity to resubmit in twelve months time if you wish it to be considered then.