You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suppose you have various messages in a DLQ but you have no time to analyse them now, so in order to avoid use the broker as a database, you would have the capability to move them to a table. There you'll can consult all the messages properties (body and headers). Given that you understood the problem in your messages, you would have a command that'd publish the messsages to the queue for processing again and django-stomp would change the state of the messages persisted in the database.
The text was updated successfully, but these errors were encountered:
Suppose you have various messages in a DLQ but you have no time to analyse them now, so in order to avoid use the broker as a database, you would have the capability to move them to a table. There you'll can consult all the messages properties (body and headers). Given that you understood the problem in your messages, you would have a command that'd publish the messsages to the queue for processing again and
django-stomp
would change the state of the messages persisted in the database.The text was updated successfully, but these errors were encountered: