Rebus.Autofac

Fixed AttachHeader bug in FakeBus.

Added 'CorrelationId' thread-local context variable to NLog logger, similar to how it's done with the Log4Net logger.

Fixed it so that the MarkedAsComplete event is raised also when a piece of saga data was never persisted - before, it was tied to the Deleted event fr

Tweaked ASB transport so that send batching kicks in only when there's 100 or more messages to send

Don't make so many DEBUG logging statements while backing off

Added ability to configure queue polling backoff strategy to low-latency mode - thanks [hagbarddenstore]

* Fixed Rabbit transport nuspec

RabbitMQ client updated - thanks [hagbarddenstore]

Made ConsoleLoggerFactory public so it can be used e.g. from processes hosting the load balancer

* Fixed logging in load balancer

Added load balancer NuGet package

Fixed SqlServerSubscriptionStorage to be able to work when publishing within a TransactionScope when it manages the connection by itself - thanks [jas

Nothing changed - pushed new version because NuGet.org had a seisure the other day and 0.54.3 wasn't properly uploaded

XmlSubscriptionStorage automatically creates directory pointed to by the subscription XML file path - thanks [hagbarddenstore]

Nudged order of disposal and logging inside Azure Service Bus transport

Change SqlServerSagaPersister and SqlServerSubscriptionStorage to use the same ConnectionHolder as SqlServerMessageQueue

Avoid ending up overflowing the stack if Console.WriteLine fails

Azure Service Bus transport: Set MaxDeliveryCount to 1000 to effectively disable built-in dead-lettering (because Rebus handles poison messages)

* Updated NLog to 2.1.0

Catch exception occurring while attempting to preserve the stack trace of a caught exception inside a TargetInvocationException. This will most likely

Made timeout manager log internal errors properly - first as warnings, and if the problem persists for 1 minute it will be logged as an error

Fix that makes changelog 0.50.0 around ToString actually true

Sent messages are no longer logged at INFO level. Both sent and received messages are now logged at DEBUG level by calling ToString on the logical mes

When delivery tracking (i.e. the tracking of message IDs across multiple delivery attempts) times out, a WARN used to be logged. That is now an INFO b

Queue transaction failures are now properly caught and will be waited out when possible

Use hybrid stash model for transaction context, allowing it to overcome thread discontinuity in ASP.NET and WCF - thanks [jasperdk]

Changed order of operations in MsmqMessageQueue that could lead to using an invalid transaction in rare circumstances

Azure Service Bus transport now automatically creates the error queue

Fixed bug where RabbitMQ transport would leak channels when used e.g. in combination with MSMQ in order to "bridge" from a MSMQ bus environment to a R

Added ability for Azure Service Bus transport to actually use MSMQ when connection string is UseDevelopmentStorage=true

Fixed race condition bug when using RabbitMQ auto-delete input queue and subscribing on another thread after having started the bus

Added ability for RabbitMQ transport to NOT create the error queue. This way, the Rebus errorQueue setting just becomes the topic under which failed m

Avoid warning when disposing one-way Azure transport

Updated Log4Net dependency to 2.0.1 (BEWARE: It appears that the Log4Net public key has changed since previous version!!)

Rebus now always adds a unique Rebus Transport ID in the headers upon sending a message. This ID will stay the same when message is deferred, forwarde

* Updated RabbitMQ dep to 3.1.5

Fixed logging when unit of work commit fails - should always be logged as a USER exception

Upgraded RabbitMQ client dependency to 3.1

Added ability to use custom encoding with the built-in JSON serializer

Timeout manager SQL persistence oddity fixed: Explicit bigint PK instead of compound thing that could potentially lead to missed timeouts - thx [krivi

Added ability to compress message bodies as well.

Fixed constantly generated warning in timeout manager - thx [hagbarddenstore]

Broke the Log4Net configuration API - sorry! But now it just adds the correlation ID to the thread context by default (i mean, why would you NOT do th

Added to SqlServerMessageQueue the ability to receive messages in prioritized order.

Update Mongo to 1.8.2 because that's the most recent version of the driver... duh!

Updated Mongo stuff to use 1.8.1 driver and no deprecated APIs

Behavior option to allow for impersonating a proper user when the user name header is present on handled messages

Special username header will flow like correlation ID if it is present

Only one SQL roundtrip to receive a message

Added transport performance showdown

Better handling of errors (i.e. DON'T IGNORE ERRORS) when MSMQ receive fails

1st go at implementing a SQL Server-based transport - can be used if you don't have MSMQ available on your machines

Made JSON serializer handle encoding properly when deserializing messages

Added configuration extension for Log4Net that will automatically set the correlation ID property on the ThreadContext

Added ability to provide correlation ID on all outgoing messages automatically in cases where none was supplied from elsewhere ('elsewhere' being eith

Added ability to let a special correlation ID header automatically flow to all outgoing messages when it is present

Fixed bug in InMemorySagaPersister that would not use the proper JSON serializer settings when deserializing