nservicebus

I am using NServiceBus v4.3, MVC4, RavenDB 2.5 and StructureMap 2.6.4 in our solution. I am having a similar issue under StructureMap to that described in this question 's responses where I require different lifecycles for the MVC Controller and NServiceBus Handler use of RavenDB's IDocumentSession in my Web project. Specifically in my case what happens is that if I use the HybridHttpOrThreadLocalScoped (as the above answer suggests for Windsor) lifecycle the sessions are not properly disposed of and I soon hit the 30 transaction limit error. If I use the HttpContext lifecycle my NSB event

I have an NServiceBus configuration that is working great on developers machines and in my Development Environment. However, when I move it to my Test Environment my messages just start getting tossed. Here is the system: An app gets a TCP message from a Mainframe system and sends it to a MSMQ (call it FromMainframe ). An application hosted in IIS has a "Handle" method for that MSMQ and processes the messages from the mainframe. In my Test Environment, step two only half way happens. The message is popped off the MSMQ, but not processed by my application. Effectively my data is LOST !

Using JOliver EventStore 3.0, and just getting started with simple samples. I have a simple pub/sub CQRS implementation using NServiceBus. A client sends commands on the bus, a domain server recieves and processes the commands and stores events to the eventstore, which are then published on the bus by the eventstore's dispatcher. a read-model server then subscribes to those events to update the read-model. Nothing fancy, pretty much by-the-book. It is working, but just in simple tests I am getting lots of concurrency exceptions (intermittantly) on the domain server when the event is stored to

I'm using NServiceBus (3.2.2), RavenDB (1.2.2017-Unstable) and Windsor (3.0.0.4001) in an MVC 4 project. I have a IHandleMessages class that handles 3 different messages, and that needs an IDocumentSession, and therefore defines a property such as: public IDocumentSession DocumentSession { get; set; } I've copied the RavenDbUnitOfWork implementation from NServiceBus' website I've registered IDocumentStore, IDocumentSession and IManageUnitsOfWork in my Windsor container as follow: container.Register( Component .For<IManageUnitsOfWork>() .ImplementedBy<RavenUnitOfWork>() .LifestyleTransient() );

What is the optimal way to configure/code NServiceBus to delay retrying messages? In its default configuration retry happens almost immediately up to the number of attempts defined in the configuration file. I'd ideally like to retry again after an hour, etc. Also, how does HandleCurrentMessageLater() work? What does the Later aspect refer to? Andreas Öhlund The NSB retries is there to remedy temporary problems like deadlocks etc. Longer retries is better handled by creating another process that monitors the error queue and puts them back into to the source queue at the interval you like. Take