Skip to content
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.

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

Exception from is-identifiable service should not DLQ messages #2082

Open
rkm opened this issue Jan 13, 2025 · 0 comments
Open

Exception from is-identifiable service should not DLQ messages #2082

rkm opened this issue Jan 13, 2025 · 0 comments
Labels
priority/high type/bug Something isn't working

Comments

@rkm
Copy link
Member

rkm commented Jan 13, 2025

Describe the bug

I encountered a scenario where the NERd socket service was not running and all incoming messages were sent to the DLQ.

Expected behavior

In this situation, the service should have exited with an exception and left the message on the queue instead.

To reproduce

Run the is-identifiable service with a socket classifier that is not available.

Additional context

@rkm rkm added needs-triage type/bug Something isn't working priority/high and removed needs-triage labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/high type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant