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

Unexpected queues added after upgrading to NServiceBus 8 #6736

Closed
saasen opened this issue May 16, 2023 · 4 comments
Closed

Unexpected queues added after upgrading to NServiceBus 8 #6736

saasen opened this issue May 16, 2023 · 4 comments
Labels

Comments

@saasen
Copy link

saasen commented May 16, 2023

Describe the bug

Description

After upgrading a SendOnly endpoint to NServiceBus 8, audit-queues started to be created. We are doing a call to AuditProcessedMessagesTo, which might be why, but should that be ignored in SendOnly endpoints?

Expected behavior

That the audit-queues are not created (?).

Actual behavior

Audit-queues are created. Not sure if this has any effect other than to create un-needed queues.

Versions

  • NServiceBus v8.0.3

Steps to reproduce

  • Create a SendOnly endpoint with version 7 of NServiceBus with Azure Service Bus transport with a call to AuditProcessedMessagesTo
  • Run the endpoint - no queues are created
  • Upgrade to NServiceBus 8 (and related packages)
  • Run the endpoint again

An .audit queue is now created, but not in use since this is a send-only endpoint.

Relevant log output

No response

Additional Information

No response

@saasen saasen added the Bug label May 16, 2023
@DavidBoike
Copy link
Member

Thanks for the bug report!

So that I can understand clearly, can I ask:

  1. If you don't use AuditProcessedMessagesTo(), no audit queue is created, right?
  2. Given the configuration mismatch between specifying an audit queue on a send-only endpoint, I assume this is one of those "well that was a weird difference" situations and that this had no ill effect on the system, correct?

@saasen
Copy link
Author

saasen commented May 22, 2023

Sure.

  1. I haven't actually tried that, but I would guess so?
  2. I haven't seen that any messages has been sent to / processed on those endpoints. So yeah, I think you are right it's just a weird difference.

However, we also call SendFailedMessagesTo() on those endpoints. An error queue is not created for send-only endpoints. I would say it's inconsistent behaviour, but it doesn't really affect anything. I was just a little afraid if all our send-only endpoints now suddenly were fully blown processing endpoints.

@DavidBoike
Copy link
Member

I've fixed the bug in #6740.

We're currently planning an NServiceBus 8.1.0 release sometime in the next few weeks and this will be included in that.

@saasen
Copy link
Author

saasen commented May 25, 2023

Thanks a lot! I appreciate the fast fix! 👏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants