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

fix: rabbitmq connection dont reconnect if the channel is closed #98

Closed
42atomys opened this issue Sep 6, 2022 · 0 comments · Fixed by #99
Closed

fix: rabbitmq connection dont reconnect if the channel is closed #98

42atomys opened this issue Sep 6, 2022 · 0 comments · Fixed by #99
Labels
aspect/backend 💻 Concerns the backend code in the repository domain/obvious 🟩 Represents the "known knowns" issue. It's Obviously priority/critical 🟥 Priority 1 - Must be fixed ASAP type/bug 🔥 Something isn't working

Comments

@42atomys
Copy link
Owner

42atomys commented Sep 6, 2022

Describe the bug

When the connection between webhooked and rabbitmq server is interrupted, webhooked dont reconnect automatically and never send events.

To Reproduce

  1. Connect to a Rabbitmq backend
  2. Kill the Rabbitmq server
  3. Start the Rabbimq again
  4. Send a webhook

What happened

Weebhooked stay with closed error eternally

Expected behavior

Webhooked needs to reconnect and send event asap

Relevant log output

4:07PM INF Webhook is processed duration=1.259667ms secure=true spec=locations-close statusCode=500 version=v1alpha1
4:07PM ERR Error during webhook processing error="Exception (504) Reason: \"channel/connection is not open\"" apiVersion=v1alpha1


### Version of software

0.5

### Environment

Docker

### Environment version

_No response_

### Additional context

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct
@42atomys 42atomys added the type/bug 🔥 Something isn't working label Sep 6, 2022
@github-actions github-actions bot added the state/triage 🚦 Has not been triaged & therefore, not ready for work label Sep 6, 2022
@42atomys 42atomys added aspect/backend 💻 Concerns the backend code in the repository state/confirmed 💜 priority/critical 🟥 Priority 1 - Must be fixed ASAP domain/obvious 🟩 Represents the "known knowns" issue. It's Obviously and removed state/triage 🚦 Has not been triaged & therefore, not ready for work labels Sep 6, 2022
@42atomys 42atomys linked a pull request Sep 10, 2022 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspect/backend 💻 Concerns the backend code in the repository domain/obvious 🟩 Represents the "known knowns" issue. It's Obviously priority/critical 🟥 Priority 1 - Must be fixed ASAP type/bug 🔥 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant