Cloud Platform


This is an IBM Automation portal for Cloud Platform 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 WebSphere Liberty
Created by Guest
Created on Apr 15, 2016

RELATED IDEAS

Liberty: Limit the number of pending requests

Our deployment has a web-services layer in Liberty connected to COBOL programs using JCICS. If the arrival rate of the requests is higher than the service rate of the servers the requests are queued in Liberty. If the clients time-out, the requests remain in the queue and they get processed by the server even though the clients are not waiting for the response. This can create a situation where the application cannot recover after a server slowdown. The problem is compounded by the fact that some of the clients retry after 30s which creates more pending requests. Even if the servers recover, the queue of pending requests may be too long to clear it in time. The only option at this time is to restart the Liberty server to clear the queue.

We are suggesting to have an attribute of the HTTP endpoint called maxPendingRequests which will limit the number of pending requests. Another option is to check that a pending request has a client listening before trying to start the thread for that request.

Idea priority Medium
RFE ID 86940
RFE URL
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Reply
    |     May 28, 2021

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests we do not see sufficient interest in this enhancement to merit delivery any time in the foreseeable future. Given the unlikelihood that we would deliver this, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Michael C Thompson <mcthomps@us.ibm.com>.

    As a mitigation, it may be possible to configure this as part of a front-end Web server, or using a ServletFilter.

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.