nservicebus

I have a handler similar to the following, which essentially responds to a command and sends a whole bunch of commands to a different queue. public void Handle(ISomeCommand message) { int i=0; while (i < 10000) { var command = Bus.CreateInstance<IAnotherCommand>(); command.Id = i; Bus.Send("target.queue@d1555", command); i++; } } The issue with this block is, until the loop is fully completed none of the messages appear in the target queue or in the outgoing queue. Can someone help me understand this behavior? Also if I use Tasks to send messages within the Handler as below, messages appear

I've been having a bit of trouble with this. Andreas Öhlund answered a question on it here , but I've been unable to get it to work using the advice he gave. Here's my setup: public abstract class CommandHandler<T> : IHandleMessages<T>, IDomainReadRepository where T : Command { public IDomainRepository DomainRepository { get; set; } protected abstract void OnProcess(T command); public TAggregate GetById<TAggregate>(Guid id) where TAggregate : IEventProvider, new() { return DomainRepository.GetById<TAggregate>(id); } public void Handle(T message) { OnProcess(message); // Domain repository will

It appears that all the sample projects that ship with nServicebus are setup where the sender and host are web roles and worker roles (and hosted via role entry point). I have a need to do something like this: Web Role sends message --> On Premise Host handles message Is it possible to configure an on premise Host to use Azure Queue storage only (and not MSMQ)? I can't seem to find a single example of this documented anywhere. Yes this is possible, you simply have to specify the transport when initializing the Bus: var config = Configure.With() .SpringBuilder() .AzureConfigurationSource() <---

i use NServiceBus as enterprise Service Bus, in the solution i'm developing i have an orchestration service which receives up to 10k messages from all client applications. I would like to improve the architecture performance and consequently enhance the solution provided. I use a Saga Data class and i would like to share the access to it between all worker threads(up to now i set just to one thread but i want to set at least to 10), what happens when multiple threads try to access the same saga istance? Does NSB already provide such a concurrency feature? Do i have to implement it on my own?

I am trying to publish a WCF service that sends to a NSB host. I have looked at the WebServiceBridge example in the NSB samples but cannot figure out how to use the NServiceBus.WcfService class in the WCF counterpart. I have found out that I can have my service interface inherit one or more IWcfService < TRequest, TResponse >, but since the service class cannot inherit multiple base classes (WcfService), is it possible to have one service implementation serve several message types? Frederik, The WCF Bridge for NServiceBus (like the Web Service Bridge) is designed to be one WCF service = one

I'm building a WCF service that receives requests on an external IP and translates them into messages that are sent via NServiceBus. One of my unit tests invokes Global.Application_Start() , which performs the configuration of the application, and then attempts to resolve the web service to validate that the container can build up all of the dependencies. This works fine when I'm using Configure.With() in my windows services, but the call to Configure.WithWeb() fails in this context (presumably because the "bin" directory does not exist?). Is it possible to unit test a method that calls

I have been struggling with this problem for a few days now and I just can't seem to figure it out. I have a simple WCF web service hosted on IIS and Windows Server 2008 R2. The implementation of the Web Service is as follows: var completionResult = new CompletionResult(); var updateTextMessage = new UpdateText { TextTemplateId = textTemplateId, Text = text }; var asyncResult = Global.Bus.Send(updateTextMessage).Register(x => completionResult = x.AsyncState as CompletionResult, null); asyncResult.AsyncWaitHandle.WaitOne(10000); if (completionResult.Messages != null && completionResult.Messages

I have an existing NServiceBus 2.6 application that I want to start moving to 3.0. I'm looking for the minimum change upgrade in the first instance. Is this as simple as replace the 2.6 DLLs with the 3.0 Nuget packages or are there other considerations? For the most part the application migration is quite straight forward, but depending on your configuration and environment, you may need to make the following changes: The new convention over configuration for endpoints may mean you will need to rename your endpoints to match your queue names (@andreasohlund has a good post about this).