minor comms logging optimization
Long polling no longer blocks an entire thread waiting for messages, but
instead internally polls the message buffer on a timer
Upgrade to Netty 4.0.24
Netty 4.0.24 supposedly fixes :poodle: so turn off our workaround
May as well start playing with the latest hazelcast while we're at it
Netty release notes are full of lying lies as far as I can tell, re :poodle:
logback brings in 1.6.2 for some reason
make all access to status happen while synchronized on service.  might help twitter passive issue
*that's* where my comm logs went