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 Mar 30, 2016

Session rebalancing and affinity switchback default value are mismatch in dynamic cluster

WAS default dynamic cluster settings are following.
#1. HttpSessionRebalanceOff=false (*1) : this indicates that
session rebalancing is ON.
#2. NoAffinitySwitchBack=false (*2) : this indicates that
affinity switchback is ON. In other words, when original server is
active, the request is routed back to original server.
(*1) "HTTP session rebalancing"-"Session rebalancer
(*2) "Session management custom
These settings combination is meaningless. And also it is
described in above Knowledge Center "Session rebalancer configuration"
section like following.
"Set the HttpSessionRebalanceOff dynamic cluster custom
property to true to explicitly disable session rebalancing for a
cluster. The default value of this custom property is false for
WebSphere Application Server dynamic cluster. If session replication is
enabled for a dynamic cluster and the HttpSessionRebalanceOff custom
property is set to false, the ODR performs session rebalancing. Session
rebalancing can be turned off by setting this custom property to true.
When using session rebalancing, ensure that NoAffinitySwitchBack=true is
set on all dynamic cluster members."

Could you update dynamic cluster's default property to
[HttpSessionRebalanceOff=true and NoAffinitySwitchBack=false] or
[HttpSessionRebalanceOff=false and NoAffinitySwitchBack=true]?
Additionally, when changing one of those properties,
administrator couldn't find above dependency. When administrator changes
HttpSessionRebalanceOff=true, does WAS automatically change
NoAffinitySwitchBack=false and vice versa?

Idea priority High
RFE ID 86211
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Jan 28, 2022

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