Skip to Main Content
Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

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 <>.