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
It was observed that creating new producer or consumer client using azure_identity::DefaultCredential would fail with the following error, but connecting using the connection string still works fine.
Error: Error { context: Custom(Custom { kind: Other, error: Status(StatusError { code: StatusCode(500), description: Some("The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101") }) }) }
The above error could result in an idling connection which could end up with another error
Error { condition: ConnectionError(ConnectionForced), description: Some("The connection was inactive for more than the allowed 60000 milliseconds and is closed by container 'LinkTracker'. TrackingId:, SystemTracker:gateway5, Timestamp:2024-01-08T15:05:08"), info: None }
While this problem was observed when upgrading the dependency azure_core to "0.19", I have experienced the same error with version "0.18" and the dotnet SDK on my local machine (mac) and an Azure VM. The dotnet SDK seems just hang forever and the message is never sent to the Event Hub.
The text was updated successfully, but these errors were encountered:
It was observed that creating new producer or consumer client using
azure_identity::DefaultCredential
would fail with the following error, but connecting using the connection string still works fine.The above error could result in an idling connection which could end up with another error
While this problem was observed when upgrading the dependency
azure_core
to"0.19"
, I have experienced the same error with version"0.18"
and the dotnet SDK on my local machine (mac) and an Azure VM. The dotnet SDK seems just hang forever and the message is never sent to the Event Hub.The text was updated successfully, but these errors were encountered: