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
Created by Guest
Created on Jul 8, 2018

Stale http session access during rollout update in case one browser requests multiple requests in a same time.

Today, web application architecture has changed from old style
Web 1.0 to Web 2.0, AJAX, Single Page Application architecture and so
on. Especially in new web application architecture, an application's
client/browser side may call multiple requests to server side WAS in a
same time. Multi browser window application or multi frame application
may also be happen multiple requests from a certain client/browser in a
same time.
In those situation, if rollout update execute, error may happen
related to session take over. Please see attached file which describes
the mechanism of session fail over error. This error condition is
happen during not only rollout update but also HTTP session rebalancing
in default dynamic cluster configuration.
The root cause of the error is 2 requests from same browser in
a same time are dispatched different application servers.
We would like to complete rollout update successfully in those
situation. We would like to update WebSphere, for example, to dispatch
the second request to the same application server during the first
request is in-flight server transaction.

Idea priority High
RFE ID 122190
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Dec 8, 2021

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests and the fact we provide Application Editioning to address this scenario, 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 <>.