limiting connections as well as allowing if all limits are reached

Why not just set your pools to use the least connections load balancing method? This will cause load balancing to occur based on the number of connections and you won't have to worry about code getting in the way and causing unnecessary over head.

 

 

Least Connections (member): Specifies that the system passes a new connection to the node that has the least number of current connections in the pool. This method works best in environments where the servers or other equipment you are load balancing have similar capabilities. This is a dynamic load balancing method, distributing connections based on various aspects of real-time server performance analysis, such as the current number of connections per node or the fastest node response time.

 

 

 

You may also want to set a slow ramp time on the pool to keep a pool member from being flooded when it gets marked up by the monitor.

 

 

 

 

 

Slow Ramp Time: Specifies the duration during which the system sends less traffic to a newly-enabled pool member. The amount of traffic is based on the ratio of how long the pool member has been available compared to the slow ramp time, in seconds. Once the pool member has been online for a time greater than the slow ramp time, the pool member receives a full proportion of the incoming traffic. Slow ramp time is particularly useful for the least connections load balancing mode.