nservicebus

问题 I have an exsiting application that works fine on a windows 2003 server. I having been moving it to windows 2008r2 and when the application trys to access the queue it gets the below error? The Indentity user of my app pool has full control of my message queue. Does anyone have any ideas on how to fix this. I believe this to be server config issue. [MessageQueueException (0x80004005): Access to Message Queuing system is denied.] System.Messaging.MQCacheableInfo.get_ReadHandle() +221 System

问题 I want my endpoint to send out an event whenever a detects a file in a specific folder is dropped. I was able to get it to work by using a class which implements IWantToRunWhenBusStartsAndStops, which in turn sets up a FileSystemWatcher to monitor the given folder. My questions is, is this the best way to go about this with nservicebus or am I missing something that may cause me trouble down the line? Here is my code: public class FileSystem : IWantToRunWhenBusStartsAndStops { private

问题 Let's say I have a ClientRequestMessage message that contains a request for a specific Client . A web application will generate these requests and they need to be sent to the correct Client for handling. I can think of a few options for this. I could have a single queue that all messages go to and specific client handlers check a property (like ClientId ) to decide whether they care about it. This feels wrong on many levels to me though. I could publish a message to all of the clients and

问题 I'm trying to wire up my first Saga, and have been unable to get the receiving endpoint to handle start message properly. I get the following exception: SagaMessageHandler Failed handling message. Spring.Objects.Factory.UnsatisfiedDependencyException: Error creating object with name 'NServiceBus.Sagas.Impl.SagaMessageHandler' : Unsatisfied dependency expressed through object property 'Persister': There are 2 objects of Type [NServiceBus.Saga.ISagaPersister] for autowire by type, when there

问题 One of our agents has a job that runs every 5 seconds, which seems to stop for no apparent reason. There are no exceptions being thrown, another scheduled task, a heartbeat that confirms that the agent is running correctly, still works, and there are no error messages in the windows event log. The scheduled task runs correctly for a few days, but then stops for no apparent reason, as if the scheduler forgets to start the task again. I have no debug information, since there are none, so my

问题 One of our agents has a job that runs every 5 seconds, which seems to stop for no apparent reason. There are no exceptions being thrown, another scheduled task, a heartbeat that confirms that the agent is running correctly, still works, and there are no error messages in the windows event log. The scheduled task runs correctly for a few days, but then stops for no apparent reason, as if the scheduler forgets to start the task again. I have no debug information, since there are none, so my

问题 I am using NServiceBus 3.2.2.0, trying to test distributor and worker in same machine. I noticed distributor is creating following queues EndPointQueue EndPointQueue.distributor.control EndPointQueue.distributor.storage EndPointQueue.retries EndPointQueue.timeouts And worker is creating a new queue something like: EndPointQueue.5eb1d8d2-8274-45cf-b639-7f2276b56c0c Is there a way to specify worker end point queue name instead of worker creating a queue by prefixing random string with end point

问题 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? 回答1: The NSB retries is there to remedy temporary problems like deadlocks etc. Longer retries is better handled by creating another process that

问题 Is NServiceBus a ESB or lightweight ESB at all? or is it more like WCF with durable/ reliable messaging? It looks to me more like a messaging framework than ESB. just want some pointer as I am just started looking into different ESB products and what they are able to do or not. 回答1: NServiceBus is definitely an ESB. Full Stop. Enterprise Service Bus, a Bus, meaning a thing that allows, by design, for components of a system to be distributed and work independently. The bus itself is also

问题 What is the correct way to swap out MSMQ transport layer to leverage another transport technology under the hood from within the NServiceBus 2.0 API? 回答1: Andreas Ohlund (@andreasohlund) answered my question on twitter with the following: "You should go for the NServiceBus trunk and implement IMessageQueue (see the Azure queue impl for reference)" NServiceBus trunk (CodeBetter TeamCity) Blog post by Andreas Ohlund on NServiceBus Azure transport layer implementation. 来源： https://stackoverflow