Using NuGet I upgraded all the NServiceBus references in a project from 3.0.3 to 3.2.2 For the 4 services in this solution I also gave them references to NServiceBus.Host from NuGet
I deployed the binaries to a test environment, and the services now startup but then fail after some time with the error below. Is there some additional configuration required in 3.2?
Unhandled Exception: Magnum.StateMachine.StateMachineException: Exception occurr ed in Topshelf.Internal.ServiceController`1[[NServiceBus.Hosting.Windows.Windows Host, NServiceBus.Host, Version=3.2.0.0, Culture=neutral, PublicKeyToken=9fc3864 79f8a226c]] during state Initial while handling OnStart ---> System.Exception: E xception when starting endpoint, error has been logged. Reason: An exception was thrown while invoking the constructor 'Void .ctor(Raven.Client.IDocumentStore)' on type 'RavenTimeoutPersistence'. ---> Autofac.Core.DependencyResolutionExcept ion: An exception was thrown while invoking the constructor 'Void .ctor(Raven.Cl ient.IDocumentStore)' on type 'RavenTimeoutPersistence'. ---> System.Net.WebExce ption: Unable to connect to the remote server ---> System.Net.Sockets.SocketExce ption: No connection could be made because the target machine actively refused i t
In 3.2 the TimeoutManager is on by default so you need to turn it off to avoid using Raven. Configure.DisableTimeoutManager()
My instance is creating an error message I believe falls under the same question, but it creates the following message --
I'm not sure why it is trying to connect to port 8080 in the local machine. Also, even though nothing is running on port 8080, why is it failing?
Do I have to have an instance of RavenDB running on port 8080 for this to work? Here is the actual exception that I am getting ...
UPDATE:
So after going through all the frustration, it seems that NServiceBus was trying to connect to the RavenDB using the port 8080. Because I had RavenDB installed already for some other projects, it seemed that "RuMeFirst.bat" figured it wouldn't use the NServiceBus provided db (maybe?) and instead wanted to use my previous install. Problem was, my original installation of RavenDB was running on port 8079 (I think that's the default for RavenDB). So when I would run NServiceBus with just a simple EndpointConfig class as a server, it wouldn't find anything on port 8080 and wouldn't want to run.
Moral of the story: Remove RavenDB before installing NServiceBus OR run RavenDB on port 8080 and then install NServiceBus to remove any of these errors that I got originally.