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
Describe the bug
In justsaying version 6.0.5, once the event bus starts listening to sqs queue, the listenloop() in SqsNotificationListener gets triggered and it polls for messages from the queue. Even if the queue gets deleted , it keeps on polling and logs the exception as this queue does not exist.
Steps To reproduce
After the eventbus start listening, delete the queue from AWS.
Expected behaviour
If queue does not exist, polling should stop or client should be given the control on how to handle the exception.
Actual behaviour
Keep on polling even the queue does not exist. All Exceptions are caught and logged within the justsaying library and there is no way for the client to handle the exceptions.
System information:
OS: MacOS
Library Version - 6.0.5
.NET6
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
In justsaying version 6.0.5, once the event bus starts listening to sqs queue, the listenloop() in SqsNotificationListener gets triggered and it polls for messages from the queue. Even if the queue gets deleted , it keeps on polling and logs the exception as this queue does not exist.
Steps To reproduce
After the eventbus start listening, delete the queue from AWS.
Expected behaviour
If queue does not exist, polling should stop or client should be given the control on how to handle the exception.
Actual behaviour
Keep on polling even the queue does not exist. All Exceptions are caught and logged within the justsaying library and there is no way for the client to handle the exceptions.
System information:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: