Set this property to support automatic retries that ignore an existing load balancer "assignment". If a user has connected to a Flynet server that has been placed on hold, this enables the automatic removal of the load balancer affinity cookie so that the next connect will be reassigned to a different server.
When multiple Flynet servers are accessed through a load balancer (to support automatic selection when more than one server provide access), the load balancer should be configured to use an HTTP cookie as the client affinity mechanism.
Once a user has started to use a particular server in this environment, he or she will continue to access that server for the duration of a browser session. If the targeted server is placed on hold, closing the browser is the only way to clear the session cookie used by the load balancer, otherwise the user sees the "No sessions available-server on hold" message. With this option, however, closing the browser will not be necessary, as the cookie will be deleted if any message indicating a full server or on-hold server is sent during a connection attempt.
For example using the IIS Application Request Routing default cookie name, this value would be ARRAffinity
Default Value: null / empty
