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
from time to time we see this:
There seems to be a message that was not acked. That blocks the ledger from being deleted as no TTL is set in order no to lose any messages in case the consuming service is not up.
Restarting the consuming service usually does fix the situation
What can cause this situation and how can we solve it?
Why is there a non-acked message while the backlog on the queue is 0?
Why is the message not discarded?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
from time to time we see this:
There seems to be a message that was not acked. That blocks the ledger from being deleted as no TTL is set in order no to lose any messages in case the consuming service is not up.
Restarting the consuming service usually does fix the situation
What can cause this situation and how can we solve it?
Why is there a non-acked message while the backlog on the queue is 0?
Why is the message not discarded?
All reactions