From EAP 6.2 and on, the web services layer reports a WARN log on the logs when a handler chain file exists, but declares no handler chain. As such, we are removing this, which has the same effect as the current behavior, but won't generate any warns.

…nodes when specifying a consumer so that users' requests can be spread across a pool of available producer nodes
Simple load-balancing strategy using a simple round-robin algorithm
Simple failover capability: if a producer node is down, the consumer will try to move requests to the next available one transparently
Sticky session support: users that started interacting with a specific producer node will stay assigned to it as long as the producer node stays up
Cooldown period for down producer nodes: producer can automatically be re-added to the available pool after a configurable cooldown period