Comment 1 for bug 455137

This may be similar to this bug:
http://bugs.mysql.com/bug.php?id=43278
The mysql proxy used to hang when running against mysqlslap (and also against drizzleslap using the mysql compatible mode)

The fix there was
http://bazaar.launchpad.net/~mysql-proxy-developers/mysql-proxy/trunk/revision/708

Basically increasing
listen(con->fd, 8) to
listen(con->fd, 128)

But looking at the drizzle code, that value is not hardcoded:

I found in drizzled/plugin/listen_tcp.cc
this line:

if (listen(fd, (int) back_log) < 0)

and I found that "back_log" is a parameter you can pass to drizzled on startup (or in drizzle.cnf) as --back_log

$ ./sbin/drizzled --help | grep -i back_log
  --back_log=# The number of outstanding connection requests Drizzle can
back_log 50

Lee: Could you see if http://hudson.drizzle.org/view/Drizzle-staging/job/Drizzleslap-staging/ is passing any value for back_log?

Thanks

Diego