BlockingConnection hearbeat

Hello, I need your help. Cannot figure out solution. I’m using Rabbitmq docker container with my python app.

About 10 min after running I having exception in my app:

pika.exceptions.ConnectionClosed: (-1, 'EOF')

Following log in rabbitmq docker:

2018-05-27 11:05:25.296 [warning] <0.1795.0> closing AMQP connection <0.1795.0> (172.18.0.1:58040 -> 172.18.0.2:5672):
missed heartbeats from client, timeout: 60s

Here is my producer code:

class Producer(object):
    EXCHANGE_TYPE = "direct"
    EXCHANGE_DURABLE = True

    def __init__(self, url, exchange):
        self._connection = pika.BlockingConnection(pika.URLParameters(url))
        self._channel = self._connection.channel()

        self._exchange = exchange
        self._channel.exchange_declare(
            exchange=self._exchange,
            exchange_type=self.EXCHANGE_TYPE,
            durable=self.EXCHANGE_DURABLE
        )

    def publish(self, route, data):
        self._channel.basic_publish(exchange=self._exchange, routing_key=route, body=data)

    def close(self):
            self._channel.close()
            self._connection.close()

url = ‘amqp://guest:guest@’+ args.rmq +‘:5672/%2F?heartbeat=0’ exchange = “my_exchange”

[lukebakken]

@farrukh-okhunov I am able to reproduce what you describe without using docker.

Please see the changes I made in this commit which shows how to ensure heartbeats are processed while using BlockingConnection.

In your code, you should enable heartbeats, and use process_data_events() periodically to ensure they are processed. Or, you could use the asynchronous publisher code here as a starting point, as it will periodically send heartbeats.

Here is a summary of what I think is affecting you:

• You attempt to disable heartbeats but they are not actually disabled due to the bug described in #1014. This is fixed in 0.12.0b3, so I would like you to test with that version.
• Rather than disabling heartbeats, you should either use SelectConnection or modify your code in a manner to what I have done here to ensure that heartbeats are processed.
• You did not see this issue using the golang code as it will process heartbeats asynchronously by default.

I am going to close this issue now but please feel free to comment and re-open it if you have further questions or find something new. Thanks again for patiently providing the information I requested.

[lukebakken]

Thanks for providing all that information. This issue may be related to #1055.

I tried to run my script with RabbitMQ which is not in Docker container. Result: everything works well.

Fixing issues that only arise in docker are not as high priority as other issues. I suggest searching docker issues or the internet for other abrupt connection closure issues - maybe there is a docker setting that needs to be adjusted?

Just as a reminder, Pika is maintained by volunteers on their spare time.