In KC we see tons of xapool messages filling up the logs, we notice these messages in the Rice logs also. Our guess is that xapool is trying to clean up already closed connections. We have currently set the logging level to fatal to prevent these from filling the logs but that is definitely not the right solution. I do not see a Rice fix version 2.1.4 so added this to 2.1.3. Please move it to 2.1.4 since 2.1.3 is going to freeze soon.