Wednesday, July 11, 2012

Running 3.x Old School

I've run into a few interesting things that I thought I'd call out after running through an upgrade on my demo project.  Here at work we want to run 3.x as we were running 2.x, but this takes some work.  There are a couple of things you need to take care of.

NHibernate Persistence Requires Different Assemblies

In order to go back to NH persistence you need to pull in the NServiceBus.NHibernate package separately.  You will also need to create your own profile that default to these settings.

        public void ProfileActivated()
            if (!Configure.Instance.Configurer.HasComponent<ISagaPersister>())

            if (!Configure.Instance.Configurer.HasComponent<IManageMessageFailures>())

            if (Configure.Instance.IsTimeoutManagerEnabled())

            if (Config is AsA_Publisher && !Configure.Instance.Configurer.HasComponent<ISubscriptionStorage>())

SLRs and Timeouts Creates Extra Queues

These features require extra queues that you didn't have in 2.x, so these need to be disabled via custom initialization.
        public void Init()

Timeout Persistence Moved to the Database

There is no more MSMQ timeout persistence, so if you want this back, you'll need to implement it yourself. This should be as simple as going back into the code and copying out the code.


  1. Adam, can you tell us about the factors that led to the decision to stay old school?

  2. We don't have full control over our deployment process and it's challenging to make changes. We also haven't successfully gotten support for RavenDB. Nothing technical, purely organizational.