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
We've been having some issues with the event-hubs client losing connection to Event Hubs and then never attempting to reconnect. Is this intended behaviour?
We construct the event-hubs client on application startup, and then reuse that client for all events that we send. Twice in the last month we've had the application permanently fail where every attempt to send returns an error with the text: amqp: link closed. I assume this means the underlying amqp client lost connection, but is it expected that it cannot recover from this? Restarting the application always resolves the issue.
I checked the package APIs and cannot see anyway of configuring this amqp connection to enable reconnecting or similar.
The text was updated successfully, but these errors were encountered:
Hey,
We've been having some issues with the event-hubs client losing connection to Event Hubs and then never attempting to reconnect. Is this intended behaviour?
We construct the event-hubs client on application startup, and then reuse that client for all events that we send. Twice in the last month we've had the application permanently fail where every attempt to send returns an error with the text:
amqp: link closed
. I assume this means the underlying amqp client lost connection, but is it expected that it cannot recover from this? Restarting the application always resolves the issue.I checked the package APIs and cannot see anyway of configuring this amqp connection to enable reconnecting or similar.
The text was updated successfully, but these errors were encountered: