NserviceBus – another day another configuration nightmare

Posted: 2014-11-18 in Code and Computers
Tags: ,

So I spend a lot of time with NServicebus and one thing I have come to recognise is that it is a configuration nightmare. Actually truth be told I no longer like dealing with NServicebus simply because during each month that passes I need to learn another way to configure something that was already configured.

Case and point.
Start NServiceBus and greated with
”  Additional information: NServiceBus performance counter for Critical Time is not set up correctly. “


Today just trying to add a send only to a project running we again ran into many problems. We run a standalone service so in the first call added this

private static void SetupTheStupidBus()
{

var configuration = new BusConfiguration();

configuration.UsePersistence<InMemoryPersistence>(); 

configuration.PurgeOnStartup(false);

Bus.CreateSendOnly(configuration);

}

First and for most https://github.com/Particular/NServiceBus/issues/2514
So add this line

configuration.DisableFeature<CriticalTimeMonitoring>();

doesn’t help won’t until 6.0.0

The recommendation is to install the counters?!?!? I don’t want these but am kind of stuck.

So “Please run Install-NServiceBusPerformanceCounters cmdlet to rectify this problem.”

Fails…. Seems I can’t do this as I don’t have the Nservice power shell installed so in the package manger console…

Install-Package NServiceBus.PowerShell

Then back to powershell (run as administrator) go to the packages folder, you should now have the powershell nugget package go into this then run

ImportModule .\lib\net40\NServiceBus.PowerShell.dll

Then in powershel lgo to the packages folder, you should now have the powershell nugget package go into this then run

Install-NServiceBusPerformanceCounters
…. Creating counters

Excellent. I guess I’ll have to repeat this on the servers, I’m sure that will go over well with the administrators.

Advertisements
Comments
  1. imorital says:

    NServiceBus really is a time sink when it comes to configuration. I’m currently working on upgrading one of our solutions from NSB 4.7 to 5.2. The 5.2 is relevant since there are API changes between 5.0 and 5.2.

    Incredible.

    I would certainly think twice before recommending this product to any future client, it doesn’t seem production ready to me.

  2. […] Yep, this seems fair: NserviceBus – another day another configuration nightmare. […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s