Bot releases are hidden (Show)
Published by SimonCropp almost 11 years ago
This release consist of these issues that were achieved through these commits.
Hot fix release for 4.3.1
The trial expiration dialog has a typo in the explanation text.
In NSB 4.3 the trial expiry window is no longer popping up when running in the emulator, making the process hang and not allowing you to select a license either.
When using brokered transports that offer support for centralized pub/sub like RabbitMQ
and ActiveMQ
, the EndpointMappings
to specify event subscriptions are not needed. However, without it, an InvalidOperation exception was being thrown.
When you specify a base event in the IAmStartedByMessages<T>
and a derived event is being published the saga does not start.
You can download this release from:
Published by SimonCropp almost 11 years ago
This release consist of these issues that were achieved through these commits.
Add the ability to send a control message to the distributor telling it to disconnect a given worker. When a worker is disconnected no work will be sent to it and ready messages for that worker will be ignored until it reconnects with a new "worker-session-id".
Users should be writing satellites instead.
Exception patching is required before rethrowing
To avoid polluting CLR types with our own convenience extension methods.
To make it easier for users we should skip checking binary versions and instead do:
if UpgradeProtectionExpiryDate>= Now OR UpgradeProtectionExpiryDate >= ReleaseDateOfBinaries => ok
Royalty free license has an expiry date of 31/12/9999 12:00:00 AM
After adding the one day grace period, an OutOfRangeException
is thrown by ExpiryChecker.IsExpired
Due to message CorrelationId
not being sent
Due to the use of local time instead of universal time.
Due to the static ExtensionMethods.CurrentMessageBeingHandled
not being correctly handled int he pipeline
Due to a missing null check on GatewayConfig
Causing ObjectDisposedException
Due to incorrect Dispose order
Caused difficulty debugging and stepping through NServicebus assemblies
Due to incorrectly attempting to deserialization them.
Will now skip deserialization and continue the pipeline.
If in the domain the following abstract class is defined, the bus will during the startup cause a NullReferenceException
Due to incorrect registry entry being checked
If a message handler throws an Exception
whose Message
property throws an Exception
then NServiceBus.Host.exe crashes with a corrupted stack. This causes the endpoint to crash.
You can download this release from: