From 5eebab1fe58af309460cc7251313131a7c63c364 Mon Sep 17 00:00:00 2001 From: d-ph Date: Sun, 22 Jan 2017 19:09:25 +0000 Subject: [PATCH 1/2] Mention the issue with rabbitmq's heartbeat and long running tasks. --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index a4df9cc5..ba4cfa3c 100644 --- a/README.md +++ b/README.md @@ -184,6 +184,9 @@ by default to avoid possible breaks in applications already using this bundle. It's a good idea to set the ```read_write_timeout``` to 2x the heartbeat so your socket will be open. If you don't do this, or use a different multiplier, there's a risk the __consumer__ socket will timeout. +Please bear in mind, that you can expect problems, if your tasks are generaly running longer than the heartbeat period, to which there are no good solutions ([link](https://github.com/php-amqplib/RabbitMqBundle/issues/301)). +Consider using either a big value for the hearbeat or leave the heartbeat disabled in favour of the tcp's `keepalive` (both on the client and server side) and the `graceful_max_execution_timeout` feature. + ## Producers, Consumers, What? ## In a messaging application, the process sending messages to the broker is called __producer__ while the process receiving those messages is called __consumer__. In your application you will have several of them that you can list under their respective entries in the configuration. From cfab13e3645e4aff67e4ef7a8f5b7095b66361e4 Mon Sep 17 00:00:00 2001 From: d-ph Date: Sat, 23 Sep 2017 16:26:15 +0100 Subject: [PATCH 2/2] Mention the issue with rabbitmq's heartbeat and long running tasks. Correct typos. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 30a6a821..20ab369b 100644 --- a/README.md +++ b/README.md @@ -184,8 +184,8 @@ by default to avoid possible breaks in applications already using this bundle. It's a good idea to set the ```read_write_timeout``` to 2x the heartbeat so your socket will be open. If you don't do this, or use a different multiplier, there's a risk the __consumer__ socket will timeout. -Please bear in mind, that you can expect problems, if your tasks are generaly running longer than the heartbeat period, to which there are no good solutions ([link](https://github.com/php-amqplib/RabbitMqBundle/issues/301)). -Consider using either a big value for the hearbeat or leave the heartbeat disabled in favour of the tcp's `keepalive` (both on the client and server side) and the `graceful_max_execution_timeout` feature. +Please bear in mind, that you can expect problems, if your tasks are generally running longer than the heartbeat period, to which there are no good solutions ([link](https://github.com/php-amqplib/RabbitMqBundle/issues/301)). +Consider using either a big value for the heartbeat or leave the heartbeat disabled in favour of the tcp's `keepalive` (both on the client and server side) and the `graceful_max_execution_timeout` feature. ### Dynamic Connection Parameters ###