Inefficient MSMQ load balancing

Just FYI, the idle timeout is fully configurable, client and server side.

 

 

Also, in the scenario described above, there is an affinity between the web and queue servers, created by persistence (if used) and the long session timeout (I'm assume the connection stays open longer if in use). Four new web connections would create a four single connections, one from each web server to one queue server. The load on the queue server is determined by how many transactions are posted on the single related web server. I doubt a lower timeout on the F5 would help much here.