docs.particular.net | All content for ParticularDocs

I have an Azure function and I'm trying to send a message with NServiceBus using Azure ServiceBus transport.

I have successfully got it working following this doc when the endpoint name does not have a “.” or period in the name. E.g.: ASBTriggerQueue

However, my endpoint name has a period, “.” and I do not have control to change the endpoint name.

With period in the name I get the following error:

The ‘NServiceBusFunctionEndpointTrigger-asb.triggerqueue’ function is in error: ‘NServiceBusFunctionEndpointTrigger-a sb.triggerqueue’ is not a valid function name.

Is anyone aware of workarounds to fix this issue?

I'm using NServiceBus with SQL Persistance and MSSQL Server.

I want to be sure that I don't get invalid data in my database in high concurrent scenarios.

From the docs I know that the SQL persister uses pessimistic concurrency since version 4.1.1. But I'm not sure how it works exactly because under "Starting Saga" and "Changes to Saga state" only optimistic concurrency is mentioned.

Does each saga instance only handle one message at a time and all the remaining messages are waiting in the queue to be handled by the saga?

Also is it possible to configure the concurrency to use optimistic concurrency instead of pessimistic concurrency for the SQL persister?

Using NServiceBus v7.4.6 plus .NET Core 3.1 and getting the exception

The given key NServiceBus.RecoverabilitySettings was not present in the dictionary.

with the code below when trying to get RecoverabilitySettings in the feature. What could be wrong?

I've been trying to get NServiceBus.Router working to allow endpoints using the AmazonSQS transport and the AzureServiceBus transport to communicate with each other. So far, I am able to get a command sent from the ASB endpoint through the router and handled by the SQS endpoint. However, when I publish an event from the SQS endpoint, it is not handled by the ASB endpoint even though I have registered the SQS endpoint as a publisher. I have no idea what I'm doing wrong, but looking at every example I can find from from the docs, it seems like it should work.

I have already tried adding another forwarding route in the reverse of what is below (SQS to ASB), but that did not solve the issue.

The endpoints and router are each running in .net 5 worker services.

I've made a sample project that reproduces the issue here, but here are some quick at-a-glance snippets that show the relevant setup:

Router Setup

I have an instance of NServiceBus that is used for multiple queues. Now I have only one queue that requires a special type of delay retries and a custom policy. In this queue I have a 3rd party call, and I want it to be retried 10 times with a specific pattern of time interval.

I have read the documentation about delayed retries, my understanding is that it will affect all the queues, not only the one I want. How this can be implemented?

I'm using NServiceBus with RabbitMq for testing envs and Azure Service Bus for prod envs.

I have a MessageHandler with a custom attribute on it. The behavior I'm testing does something based on the value of that attribute. The NServicebus documentation only gives unit tests examples of a behavior based on a mocked handler. How can I use my own fake or is there an other way I should test my behavior?

I need to query a property of Saga Data class to get a list. It is stored on SqlPersistance table [Data] column as a serialized object. Think about a scenario that my SagaData has a property called UserName, so I want to query every saga related to that user. In a sloppy way, I can query the column content, get the list and can create Saga objects out of the content, by querying like:

Consider this extremely simple .NET Core 3.1 (and .NET 5) application with no special config or hosted services:

NServiceBus docs say:

The Timeout Manager is enabled by default. However, it is automatically disabled for send-only endpoints and transports that support delayed delivery natively (i.e. Azure Service Bus).

SQL supports delayed messaging, yet max delay is 15 minutes.

Is NSB clever enough to figure out that requested timeout period exceeds max SQS interval and switch back to Timeout Manager? Or is it possible to force NSB to use Timeout Manager and ignore transport capabilities?