title: Celery and RabbitMQ timeouts and connection resets
body: <p>I'm using RabbitMQ 3.6.0 and Celery 3.1.20 on a Windows 10 machine in a Django application. Everything is running on the same computer. I've configured Celery to Acknowledge Late (<code>CELERY_ACKS_LATE=True</code>) and now I'm getting connection problems.</p>
  
  <p>I start the Celery worker, and after 50-60 seconds of handling tasks each worker thread fails with the following message: </p>
  
  <blockquote>
    <p>Couldn't ack ###, reason:ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)</p>
  </blockquote>
  
  <p>(### is the number of the task)</p>
  
  <p>When I look at the RabbitMQ logs I see this:</p>
  
  <blockquote>
    <p>=INFO REPORT==== 10-Feb-2016::22:16:16 ===
    accepting AMQP connection &lt;0.247.0> (127.0.0.1:55372 -> 127.0.0.1:5672)</p>
    
    <p>=INFO REPORT==== 10-Feb-2016::22:16:16 ===
    accepting AMQP connection &lt;0.254.0> (127.0.0.1:55373 -> 127.0.0.1:5672)</p>
    
    <p>=ERROR REPORT==== 10-Feb-2016::22:17:14 ===
    closing AMQP connection &lt;0.247.0> (127.0.0.1:55372 -> 127.0.0.1:5672):
    {writer,send_failed,{error,timeout}}</p>
  </blockquote>
  
  <p>The error occurs exactly when the Celery workers are getting their connection reset.</p>
  
  <p>I thought this was an AMQP Heartbeat issue, so I've added <code>BROKER_HEARTBEAT = 15</code> to my Celery settings, but it did not make any difference.</p>