-
Notifications
You must be signed in to change notification settings - Fork 481
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
Dapr Sidecar fails to publish message to azure service bus #3559
Comments
Can you try this with Dapr 1.14.4? The SDK for ASB was updated and it includes some fixes that may be relevant to what you're seeing. |
Yes I will update to 1.14.4 and test that out. |
Now running 1.14.4. Haven't been running long enough to be confident the Service bus error is gone, will keep monitoring. I am now seeing this new type of message in the logs. Is there any way to figure out what operation failed from the daprd logs? |
Still seeing this error with 1.14.4 |
Looking at our logs in more detail, from our code, we catch the timeout ex. We then build a new dapr client and try again. We will try 3 times before giving up. The curious thing is that our logs all have the same timestamp. I assumed I am not sure, but I think the next call we make to publish the next message to the service bus succeeds. I think this since our logs are not full of errors publishing to the service bus. daprd error
C# logs.
|
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
Not stale |
Expected Behavior
Dapr service bus component should be able to publish messages to the azure service bus.
Actual Behavior
After a period of running, the Dapr Sidecar contains logs indicating a failure.
Using Dapr 1.13.5 in AKS.
Steps to Reproduce the Problem
Unable to repo on demand. Pods run for a while then errors appear.
Possibly related to #2617 ?
The text was updated successfully, but these errors were encountered: