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

AMQP Integration doesn't reestablish connection if channel was closed #687

Open
2 tasks done
DennisK92 opened this issue May 30, 2022 · 0 comments
Open
2 tasks done

Comments

@DennisK92
Copy link

DennisK92 commented May 30, 2022

  • The issue is present in the latest release.
  • I have searched the issues of this repository and believe that this is not a duplicate.

What happened?

When restarting the AMQP server, all client channels are closed. The application server AMQP integration does not reestablish a connection to the AMQP server unless the application server is restarted.

What did you expect?

When the channel to the AMQP server is closed, the application server should try to establish a new connection instead of logging errors and not transmitting uplinks anymore.

Steps to reproduce this issue

Steps:

  1. Close the AMQP connection on serverside
  2. Check the logs on the application server or that messages aren't coming through anymore.
  3. Restart application server to resolve the issue.

Could you share your log output?

time="2022-05-30T13:46:42.486957131Z" level=info msg="integration/amqp: publishing event" ctx_id=1f5a323f-05d3-48d6-87f9-ccd821c7d333 routing_key=application.1.device.a81758fffe057092.event.up
time="2022-05-30T13:46:42.486990232Z" level=error msg="integration/multi: integration error" ctx_id=1f5a323f-05d3-48d6-87f9-ccd821c7d444 error="publish event error: Exception (504) Reason: \"channel/connection is not open\"" integration="*amqp.Integration"

Your Environment

Component Version
Application Server v3.17.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant