Bot releases are hidden (Show)
Published by timbussmann about 8 years ago
As part of this release we had 7 commits which resulted in 2 issues being closed.
Bugs
Improvements
You can download this release from nuget
Published by SimonCropp over 9 years ago
When utilizing Second Level Retires and using NHibernate Timeout Persister with a SQL server database, messages are being truncated to 8000 bytes prior to being persisted to the TimeoutEntity table. The following message is logged:
The fix was to explicitly set type of the column to NHibernateUtil.BinaryBlob in the mapping class.
As part of this release we had 3 commits which resulted in 1 issue being closed.
You can download this release from nuget
Published by SimonCropp almost 10 years ago
As part of this release we had 159 commits which resulted in 44 issues being closed.
Streams added in this release:
MessageHasFailedAFirstLevelRetryAttempt
MessageHasBeenSentToSecondLevelRetries
MessageSentToErrorQueue
Msmq in workgroup mode requires TTRQ to be set when sending.
http://serverfault.com/questions/480285/how-to-change-default-msmq-time-to-reach-queue-time
Exposed a key on the connection string ...;TimeToReachQueue=12:00:00;
where the value is a parsable timespan.
If a modification of the Saga Id then an exception will be thrown
A modification of IContainSagaData.Id has been detected. This property is for infrastructure purposes only and should not be modified. SagaType: TheSagaType
Since an instance is being passed in then there is no need for a new()
constraint
RequestTimeout<TTimeoutMessageType>(DateTime at, TTimeoutMessageType timeoutMessage)
RequestTimeout<TTimeoutMessageType>(TimeSpan within, TTimeoutMessageType timeoutMessage)
Both have new()
constraints and hence cannot be an interface. No need to construct an instance when the consumer can do this themselves.
RequestTimeout<TTimeoutMessageType>(TimeSpan within, Action<TTimeoutMessageType> messageConstructor) where TTimeoutMessageType : new()
RequestTimeout<TTimeoutMessageType>(DateTime at, Action<TTimeoutMessageType> action) where TTimeoutMessageType : new()
An ~4x improvement in the performance of InMemoryTimeoutPersister
Now doing the performance counter check (counter.CounterType
) in a time-bombed thread that if it doesn't return within 2 seconds we mark the counter as not "healthy".
As of 5.1 the Host will be on a seprarate repo/release cycle
Store Exception.ToString()
instead of Exception.StackTrace
inside the NServiceBus.ExceptionInfo.StackTrace
header
Not needed since we are locking assembly version number to major
It creates noise in the package manager console
For Transport, Logging and Persistence definitions.
ReplyToOriginator<TMessage>(Action<TMessage> messageConstructor)
incorrectly did a null parameter check whichc resulted in a null being passed ass a message.
Now support two possible was to register a custom serializer.
A user can either config.UseSerialization(type of definition)
or config.UseSerialization(type of serializerImplementation)
Fixed so when NServiceBus.MsmqUtilities.Convert
throws the message will be sent to the error queue
if Thread.CurrentPrincipal.Identity
is null (which can happen in IIS impersonation) fall back to using WindowsIdentity.GetCurrent()
instead of Thread.CurrentPrincipal.Identity
Thread.CurrentPrincipal
is now checked for null
Change IBus.OutgoingHeaders
to a ConcurrentDictionary
You can download this release from nuget
Published by johnsimons almost 10 years ago
As part of this release we had 4 commits which resulted in 2 issues being closed.
This is an endpoint generated by ServiceMatrix.
It configures the transport in a class that implements INeedInitialization
.
public class TransportConfig : INeedInitialization
{
public void Customize(BusConfiguration config)
{
config.UseTransport<NServiceBus.RabbitMQTransport>();
}
}
Content trimmed. See full issue
Double negative in distributed transaction configuration logic was causing distributed transactions to always be on even when disabled by consumer
You can download this release from nuget
Published by SzymonPobiega almost 10 years ago
As part of this release we had 1 issue closed.
Related to this change in distributor
You can download this release from nuget
Published by SzymonPobiega almost 10 years ago
As part of this release we had 1 issue closed.
Related to this change in distributor
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by andreasohlund about 10 years ago
As part of this release we had 6 commits which resulted in 2 issues being closed.
Response message can now be accessed from callback.
This bug affect version 5 only.
In prior versions it was possible to access the reply message from a callback, this seem to be broken in v5.
The following acceptance test passes against v4.6 but fails for v5:
public class When_using_callback_to_get_message : NServiceBusAcceptanceTest
{
[Test]
Content trimmed. See full issue
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
Published by indualagarsamy about 10 years ago
As part of this release we had 1 issue closed.
Messages handled by a saga that contains a explicit saga id should not be allowed to create a new saga if the given saga can't be found in storage. The saga loader has now been modified to check for the existence of the saga id header and also check that the message is directed to the specific saga by comparing the saga type with the saga type header.
You can download this release from nuget
As part of this release we had 5 commits which resulted in 5 issues being closed.
Store Exception.ToString()
instead of Exception.StackTrace
inside the NServiceBus.ExceptionInfo.StackTrace
header
When exception details are written to the error headers the InnerException
type is captured.
However the Message
and the StackTrace
of InnerException
are not captured.
Same goes for the nested InnerExceptions
and StackTrace
of AggregateException
When HandleEndMessage
or HandleBeginMessage
throw an Error
is logged
However when HandleError
is called a Warn
is logged.
You can download this release from nuget
Published by johnsimons about 10 years ago
As part of this release we fixed 2 issues.
This fixes the polarity that checks when to run the clean-up procedure
We updated NService Bus from 3.0.3.32 to 4.6.4. The old version saga stop work.
You can download this release from nuget
Published by johnsimons about 10 years ago
As part of this release we fixed 2 issues.
This fixes the polarity that checks when to run the clean-up procedure
We updated NService Bus from 3.0.3.32 to 4.6.4. The old version saga stop work.
You can download this release from nuget
Published by johnsimons about 10 years ago
As part of this release we fixed 2 issues.
This fixes the polarity that checks when to run the clean-up procedure
We updated NService Bus from 3.0.3.32 to 4.6.4. The old version saga stop work.
You can download this release from nuget