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

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 Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Sep 8, 2016

Support timeout at the request-level

We are planning to use Liberty for running online transactions on mainframe.
The model is going to be: Consumer -- > Web server (on z/) -- > Liberty app server (on z/).
As we understand, the request from the Web server first arrives at a Global queue (associated with the Liberty server). Default Executor (in the Liberty server) picks up the request, and executes it.

Our ask - If the Executor is not able to start execution of an http request within a certain time duration (either configured in request header or server.xml), then the server should forget about the request (time it out), instead of executing it.

We'd prefer that this time duration can be configured in server.xml (as a global value), but can be overridden for a particular request/application type.

Idea priority High
RFE ID 94314
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Oct 8, 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 Graham Charters <>.