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

When reposting a service bus message after a failure, the Diagnostic-Id field is not reset/clear. #44432

Closed
EmilDamian opened this issue Jun 7, 2024 · 4 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback More information is needed from author to address the issue. no-recent-activity There has been no recent activity on this issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus

Comments

@EmilDamian
Copy link

Library name and version

Azure.Messaging.ServiceBus 7.17.5

Describe the bug

When reposting a service bus message after a failure, the Diagnostic-Id field is not reset/clear.

Expected behavior

Diagnostic-Id field should be cleared.

Actual behavior

The same Diagnostic-Id values is kept for unrelated messages.

Reproduction Steps

await using var serviceBusSender = serviceBusClient.CreateSender(topicName);
await serviceBusSender.SendMessageAsync(
new ServiceBusMessage(message)
{
ApplicationProperties =
{
[configuration.ReviveForProperty] = subscriptionName,
[configuration.RetryCounterProperty] = retryCounter + 1
},
ScheduledEnqueueTime = DateTimeOffset.UtcNow.Add(TimeSpan.FromSeconds(retryDelay))
});

Environment

Azure Function App

.NET SDK:
Version: 8.0.300
Commit: 326f6e68b2
Workload version: 8.0.300-manifests.4e5ea2d8
MSBuild version: 17.10.4+10fbfbf2e

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22000
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.300\

.NET workloads installed:
[aspire]
Installation Source: VS 17.10.34928.147
Manifest Version: 8.0.0/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.0.0\WorkloadManifest.json
Install Type: FileBased

Host:
Version: 8.0.5
Architecture: x64
Commit: 087e15321b

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus labels Jun 7, 2024
Copy link

github-actions bot commented Jun 7, 2024

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@jsquire jsquire assigned jsquire and unassigned JoshLove-msft Jun 7, 2024
@jsquire
Copy link
Member

jsquire commented Jun 7, 2024

@EmilDamian: Thank you for reaching out and we regret that you're experiencing difficulties. I'm not sure that I understand the end-to-end scenario that you're describing. Can you please provide more context for what a "failure" is in this scenario and what you believe the expected behavior should be?

@jsquire jsquire added needs-author-feedback More information is needed from author to address the issue. and removed needs-team-attention This issue needs attention from Azure service team or SDK team labels Jun 7, 2024
Copy link

github-actions bot commented Jun 7, 2024

Hi @EmilDamian. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

Copy link

Hi @EmilDamian, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

@github-actions github-actions bot added the no-recent-activity There has been no recent activity on this issue. label Jun 14, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback More information is needed from author to address the issue. no-recent-activity There has been no recent activity on this issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus
Projects
None yet
Development

No branches or pull requests

3 participants