Golden nuggets of WebSphere Application Server Plugin Configuration

Set LoadBalanceWeight to a value other than default say 20.  If there are 3 clones, you might choose the starting LoadBalanceWeights to be: 20, 20, 19. After normalization the weights will be unchanged. It is recommended that all clones have same weight except one clone off by one (for example: 20, 20, 19)

Set set IgnoreAffinityRequests="false".If using Round Robin for the LoadBalance option, by default the affinity requests do NOT lower the LoadBalanceWeight (IgnoreAffinityRequests="true"). This can cause an uneven distribution across the servers in environments that make use of session affinity. But, If IgnoreAffinityRequests="false" then the weight IS lowered by each affinity request, leading to a more balanced Round Robin environment. When using Random, the affinity requests are still handled correctly (sent to same cloneid as before). But new requests are routed randomly, and the LoadBalanceWeight is not used.

<ServerCluster CloneSeparatorChange="false" GetDWLMTable="true" IgnoreAffinityRequests="false" LoadBalance="Round Robin" Name="wp_cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">

Set  GetDWLMTable to "true" If Memory-to-Memory (M2M) session replication is enabled in WebSphere Application Server.. Memory-to-Memory replication uses partition IDs rather than clone IDs. This can lead to broken session affinity if GetDWLMTable is set to false (which is the default). So it is very important to set GetDWLMTable="true" whenever using M2M in WebSphere Application Server.

Read http://www-01.ibm.com/support/docview.wss?uid=swg21318463 for more tips ...