Bit extra on the "Connecting to peers" 3.3.1.30003

[ciaobaby]

When jobs drop into "Connecting to peers" the logger pane immediately fills up with these and I have TWO build 30003 clients running, both exhibit the same symptoms and not necessarily at the same time.

[2013-08-13 14:14:16] Got unchoke from BitTorrent 7.8.1 (xxx.22.248.17:46501), can't request immediately because request queue is full (3)

............... Other log entries . Irrelevant as they are WebUI requests.

[2013-08-13 14:16:24] Got unchoke from µTorrent 3.3 (xxx.175.82.97:18456), can't request immediately because request queue is full (3)

[2013-08-13 14:16:41] Got unchoke from BitTorrent 7.2.1 (xxx.27.65.197:37158), can't request immediately because request queue is full (4)

[2013-08-13 14:17:25] Got unchoke from µTorrent 3.3.2 (xxx.2.28.244:4843), can't request immediately because request queue is full (3)

[2013-08-13 14:17:26] Got unchoke from BitTorrent 7.8.1 (xxx.22.248.17:50475), can't request immediately because request queue is full (3)

[2013-08-13 14:17:59] Got unchoke from µTorrent 3.3.2 (xxx.2.28.244:21512), can't request immediately because request queue is full (3)

[2013-08-13 14:18:21] Got unchoke from µTorrent 2.2.1 (xxx.232.191.105:25195), can't request immediately because request queue is full (2)

The rate of these log entries reduces significantly when the problem job is stopped or changes status.

Hopefully it goes without saying that these IPs are from other jobs, but I'll state it anyway.