NServiceBus | monitor better microservices with the most powerful service | Messaging library

I'm building html tables where some of the can hold extremely long text. Can I wrap it like after 100 chars it has "..." and maybe on click it would reveal the whole text?

If possible I do like to keep this current style config and just add this feature.

I'm using NserviceBus with the Azure Function project ( NServiceBus.AzureFunctions.InProcess.ServiceBus). Application is using azure service bus as the transport and it is configured in function startup by using the below code

I have this App Service in Azure running as a Web Job. The application is a former Windows Service built using NServiceBus and I have been reconfiguring it to work in Azure.

The application is using AzureServiceBusTransport and I have my Azure Service Bus with a queue set up.

I got it working... when I am using a Shared Access Key configured in my connectionstring like this;

I have a sample solution with a console and library project. Both reference the same nuget but a different version. The console project also has a reference to the library project. So the structure is like this:

As per NServiceBus Azure Cosmos DB persistence documentation, the outbox deduplication data is kept for 7 days by default. However, this can easily add hundreds of outbox documents in a day for a high volume transaction DB. I understand we can change the default settings to reduce the outbox ttl. However, before doing that, I would like to understand the following:

• What is the significance of keeping the outbox document for 7 days in Cosmos DB?
• What is the impact of reducing the ttl of the outbox document to, say, 4 days? Does it mean if a message has failed, it can be only recovered for the next 4 days? If yes, is there a way to clean up the outbox record for the transactions that are successful immediately?

How can I send a message (or publish an event) when a message runs out of retries and moves to the error queue?

When a request comes into my system, I create a Saga to track it. The Saga sends commands to Handlers to do async work. If the handler fails, I want to both move that command to the error queue (the default behavior) and send a message to the Saga to alert the client that originally requested the work.

I have tried customizing the recoverability behavior to use the Saga as the error queue, which sends the command back but does not get it into the error queue:

I'm trying to build my first NserviceBus application, but I cannot get it to work. The message arrives on the "backend" but the handler uses DI and NServicebus claims it cannot find the service for the interface. But the code was lifted directly from the examples. I'm missing something and I cannot figure it out.

The Error: dbug: NServiceBus.LoadHandlersConnector[0] Processing message type: Messages.JobStartCommand Message headers: NServiceBus.MessageId : 0044f261-e3b3-4287-b6f0-ad7400ef43cb NServiceBus.MessageIntent : Send NServiceBus.ConversationId : bb4f276f-63fe-450b-b234-ad7400ef43cd NServiceBus.CorrelationId : 0044f261-e3b3-4287-b6f0-ad7400ef43cb NServiceBus.ReplyToAddress : ClientUI NServiceBus.OriginatingMachine : L19002992 NServiceBus.OriginatingEndpoint : ClientUI $.diagnostics.originating.hostid : e1fecb2b72b8185e47341bb4dfb37dd7 NServiceBus.ContentType : text/xml NServiceBus.EnclosedMessageTypes : Messages.JobStartCommand, Messages, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null NServiceBus.Version : 7.5.0 NServiceBus.TimeSent : 2021-07-29 14:31:08:228497 Z NServiceBus.Retries : 3 NServiceBus.Retries.Timestamp : 2021-07-29 14:31:40:397277 Z Handlers to invoke: Extractor.JobStartHandler Extractor.JobStartHandler info: NServiceBus.RecoverabilityExecutor[0] Immediate Retry is going to retry message '0044f261-e3b3-4287-b6f0-ad7400ef43cb' because of an exception: System.InvalidOperationException: Unable to resolve service for type 'IExtract' while attempting to activate 'Extractor.JobStartHandler'. at Microsoft.Extensi

My backend program.cs

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?