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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.