Skip to content

Commit e6f5185

Browse files
committed
Merge branch '4.4'
* 4.4: [Messenger] Information about why consumers do not show up in the (rabbimq) admin panel
2 parents 5015a7e + 2e0b50f commit e6f5185

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

messenger.rst

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -754,6 +754,17 @@ your Envelope::
754754
new AmqpStamp('custom-routing-key', AMQP_NOPARAM, $attributes)
755755
]);
756756

757+
.. caution::
758+
759+
The consumers do not show up in an admin panel as this transport does not rely on
760+
``\AmqpQueue::consume()`` which is blocking. Having a blocking receiver makes
761+
the ``--time-limit/--memory-limit`` options of the ``messenger:consume`` command as well as
762+
the ``messenger:stop-workers`` command inefficient, as they all rely on the fact that
763+
the receiver returns immediately no matter if it finds a message or not. The consume
764+
worker is responsible for iterating until it receives a message to handle and/or until one
765+
of the stop conditions is reached. Thus, the worker's stop logic cannot be reached if it
766+
is stuck in a blocking call.
767+
757768
Doctrine Transport
758769
~~~~~~~~~~~~~~~~~~
759770

0 commit comments

Comments
 (0)