Skip to content

[Messenger] Clarify keepalive implementation for each transport #20736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 10, 2025
Merged

[Messenger] Clarify keepalive implementation for each transport #20736

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions messenger.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1729,6 +1729,13 @@ The transport has a number of options:
The message time to run before it is put back in the ready queue - in
seconds.

The Beanstalkd transport supports the ``--keepalive`` option by using Beanstalkd's
``touch`` command to periodically reset the job's ``ttr``.

.. versionadded:: 7.2

Keepalive support was introduced in Symfony 7.2.

.. _messenger-redis-transport:

Redis Transport
Expand Down Expand Up @@ -2051,6 +2058,13 @@ The transport has a number of options:
FIFO queues don't support setting a delay per message, a value of ``delay: 0``
is required in the retry strategy settings.

The SQS transport supports the ``--keepalive`` option by using the ``ChangeMessageVisibility``
action to periodically update the ``VisibilityTimeout`` of the message.

.. versionadded:: 7.2

Keepalive support was introduced in Symfony 7.2.

Serializing Messages
~~~~~~~~~~~~~~~~~~~~

Expand Down