All geek questions in one place

Problem with NServiceBus 3.2 Samples

I am trying to run a sample NServiceBus for AsyncPages. It seems simple enough.

  • Download the latest version from NServiceBus.com
  • Run the bat file to install the necessary components
  • Open solution
  • Press f5
  • Enter the number in the text box

When I do this, I get a nasty RavenDB error (NServiceBus uses this as a data store).

Exception when starting endpoint, error has been logged. Reason: There is no index named: dynamic/TimeoutData

It seems that RavenDB did not create or could not create the index. Not sure if this is a RavenDB error or an NServiceBus error, but it does not allow me to run the sample.

Thanks at Advance

Update:

When upgrading to version 3.2.1, as suggested by Andreas.

 Exception when starting endpoint, error has been logged. Reason: An exception was thrown while invoking the constructor 'Void .ctor(Raven.Client.IDocumentStore)' on type 'RavenTimeoutPersistence'.

I also notice problems with samples and TopShelf. They are placed at the top of the page, referring to the 3.2.0 version of NServiceBus instead of 3.2.1.

Not an interesting experience so far, but maybe I should just give up the samples and go straight to something.

+4
source share
3 answers

I struggled with the same problem - it turned out that NServiceBus had a problem connecting to RavenDB.

RunMeFirst.bat tries to tweak things, but apparently doesn't always succeed.

In my case, I installed RavenDB, but not on the standard port 8080, where NServiceBus is expected. Check your Raven.Server.exe.config in the Raven installation folder (default is C: \ RavenDB \ RavenDB.0.0.0 \ RavenDB.Server). The port number must be specified. If it is different, you can override the default connection string NServiceBus to RavenDB by adding web.config or app.config to your file:

 <connectionStrings> <add name="NServiceBus.Persistence" connectionString="Url=http://localhost:8081;" /> </connectionStrings>

Where 8081 is an example RavenDB connection port.

Another problem that may go wrong is that your RavenDB is in conflict with another service using port 8080 to solve this problem, you can change the port number in the Raven configuration and add a user connection string.

Hope this helps, Greetings

+3
source

Yes, we saw this problem, and it will be fixed in the next fix release (very soon). The current workaround is to call RunMeFirst.bat again.

+2
source

I had the same "RavenTimeoutPersistence" symptom that the reason RunMeFirst.bat did not execute correctly was limited to security restrictions.

  • Do not forget to right-click the NServiceBus3.2.x.zip file, then the “Unlock” property
  • The batch file must be run with administrator privileges. So, open a command prompt with "Run as administrator", then run it

After that mine worked fine.

0
source

Source: https://habr.com/ru/post/1414976/

More articles:


All Articles