NServiceBus

NServiceBus copied to clipboard

Started FeatureStartupTasks are not stopped on endpoint start failure

4

As part of `Endpoint.Start`, all defined `FeatureStartupTask`s defined by Features are started sequentially. If a subsequent startup task fails (or some other startup failure happens after all startup tasks have...

timbussmann

When using EntityFramework transactions to share transactions/connections with NServiceBus, it is not easy to determine if the code is running within NServiceBus pipeline (e.g. message handler) or outside of it....

HEskandari

In NSB v8 current seam exposes transport configuration as a POCO object which is managed by the users and passed to `UseTransport` method e.g. ```csharp var transport = new SqlServerTransport("connection-string");...

WojcikMike

### Problem Description When requesting a timeout without any data or with just a primitive type (like an integer) you need to create a value object (class) to be able...

WilliamBZA

When a user exceeds the transport limit there often a transport-specific exception is raised like `Microsoft.Azure.ServiceBus.MessageSizeExceededException`. It would be nice is the transport would rethrow this as `NServiceBus.MessageSizeExceededException` as this...

ramonsmits

The end of processing a message is captured before the message is acked in the queueing system and is causing the audit headers for processing and critical time to be incorrect

18

Since the processing and critical time headers on audit message are captured when the pipeline completes it doesn't take into account the time it takes to: - Push outgoing messages...

andreasohlund

Repro and failing test [here](https://github.com/Particular/NServiceBus/pull/5901).

HEskandari

Adjust the transport seam to ensure that incoming message modifications can't persist between immediate retry attempts

2

If the immediate retries are implemented in-memory within the transport the current transport seam makes it possible to modify the incoming message so that the effects of the modification are...

SzymonPobiega

EnclosedMessageTypes header contains proxy types

6

I noticed the following value for the header EnclosedMessageTypes: Store.Messages.Events.OrderAccepted__impl, NServiceBusMessageProxies, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null;Store.Messages.Events.OrderAccepted, Store.Messages, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null This seems incorrect. I only expected the interface type(s) but not the...

ramonsmits

Saga not found when two sagas handle same event

5

I have an endpoint with two sagas with separate state. When both of the sagas implement IHandle(SomeMessage) and the mapping is configured in ConfigureHowToFindSaga for SomeMessage, Saga A will correctly...

kevin-whalley-gc