Releases: Particular/NServiceBus
5.2.0
As part of this release we had 153 commits which resulted in 32 issues being closed.
Features
- Added support for individualizing endpoint queue names when Scaling-Out #2571
- Diagnostic support for the message processing pipeline #2211
Improvements
- IncomingContext constructor has to be public for unit testing behaviors #2635
- Exception Data property to be included when setting exception headers #2630
- Added explicit API for property injection for IHandleMessages #2603
- Added Persistence extensibility per storage type #2587
- Throw an exception when callbacks are used in Send only mode #2476
Bugs
- Configuring invalid combinations of persistence and storage types causes endpoint to fail at startup #2644
- When setting an individual storage type persistence, all storage persistence types are overridden #2622
- Support inheritance-based sagas of +1 generic args #2613
- Send only endpoints can't publish messages #2612
- Incorrect assignment of assembly ReleaseDateAttribute causes license upgrade protection to expire #2610
- ForwardReceivedMessagesTo setting does not auto enable forwarding #2604
- Cannot set up property injection in NSB 5.0 #2600
- XMLSerialization does not deserialize messages with Uri containing '&' characters #2595
- Accessing list of scanned types returns nulls for types that could not be scanned #2591
- Obsolete BusConfiguration.EndpointVersion(string version) #2589
- Better exception handling for users hosting in IIS without permissions to access ~/App_Data folder #2570
- Point to documentation on how to set-up performance counter PS cmdlet that is not found #2519
- When an event is derived from multiple interfaces that don't have a hierarchy, only handlers for the first interface are called #2301
- Having a message with a read-only collection property of the same type causes StackOverflowException in EncryptionMessageMutator #2119
- IHandleSagaNotFound fires multiple times for a message that targets multiple sagas #2080
- High Critical Time reported when a deferred message arrives. #1250
Where to get it
You can download this release from nuget
3.3.14
As part of this release we had 1 issue being closed.
Bugs
#2586 Throw from NServiceBus.MsmqUtilities.Convert will result in message loss
Fixed so when NServiceBus.MsmqUtilities.Convert throws the message will be sent to the error queue
This problem manifests when a message with invalid or corrupted headers are written to the queue causing NServiceBus.MsmqUtilities.Convert to throw when dequeuing.
Who is affected
Systems utilising external integration to create messages may be affected by this. For example systems with endpoints receiving messages from non-NServiceBus senders.
Where to get it
You can download this release from nuget
5.1.3
4.0.10
As part of this release we fixed the following bug:
Bugs
#2585 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent, for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget
4.1.7
As part of this release we fixed the following bug:
Bugs
#2584 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent, for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget
4.2.6
As part of this release we fixed the following bug:
Bugs
#2583 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent, for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget
4.5.6
As part of this release we fixed the following bug:
Bugs
#2580 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget
4.4.7
As part of this release we fixed the following bug:
Bugs
#2581 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent, for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget
4.6.9
As part of this release we fixed the following bug:
Bugs
#2579 Corrupted MSMQ Message Headers may result in message loss
Who’s affected:
Anyone using MSMQ Transport and is also doing one of the following:
- Manual editing of the headers of messages which may result in an invalid xml of the headers being sent to the endpoint.
- Anyone dealing with an integration scenario where native message are being sent for example from Java where the headers may not contain valid xml.
Symptoms:
The message will be discarded.
Where to get it
You can download this release from nuget
4.7.5
As part of this release we had 18 commits which resulted in 2 issues being closed.
Improvements
#2566 NSB 4 with Castle Windsor: Performance is slow while debugger is attached
Bugs
#2573 Throw from NServiceBus.MsmqUtilities.Convert will result in message loss
Fixed so when NServiceBus.MsmqUtilities.Convert throws the message will be sent to the error queue
This problem manifest when a message with invalid or corrupted headers are written to the queue causing NServiceBus.MsmqUtilities.Convert to throw when dequeuing.
Who is effected
Systems utilising external integration to create messages may be effected by this. Foe example systems with endpoints receiving messages from non-NServiceBus senders.
Where to get it
You can download this release from: