servicebus

How should I set rebus up for one producer and many consumers

由 醉酒当歌 提交于 2019-12-07 07:22:43
问题 I am going through the samples and reading the docs but I am still not sure of how to configure rebus for my scenario (or that using the bus is a good fit). I have one producer of Tasks to do, lets say ImportOrder and CalculateOrderPrice I want to dump messages from the producer and queue lots of these messages. I want two clients that listens to ImportOrder, and 10 clients that listens to CalculatePriceOfOrder. I do not want the same order to go to multiple endpoints at the same time, I am

Error configuring using Windows Service Bus (1.1) Configuration Wizard

由 大城市里の小女人 提交于 2019-12-07 05:09:44
问题 I am trying to configure Windows Service Bus (1.1) using Service Bus Configuration Wizard. I am getting below error when I try to configure it. Can anybody tell me what is the problem. [Error] [5/9/2014 9:32:40 AM]: System.Management.Automation.CmdletInvocationException: Starting service Service Bus Gateway on machine USHP2-10-056A failed: Time out has expired and the operation has not been completed. ---> Microsoft.ServiceBus.Commands.Common.Exceptions.OperationFailedException: Starting

Azure WebJob concurrency when using ServiceBusTrigger

由 余生颓废 提交于 2019-12-07 04:07:21
问题 I have been using Azure Storage Queues to feed a WebJob, using the QueueTrigger attribute. I configure my QueueTrigger to dequeue a number of items for concurrent processing, like this: public static void Main() { JobHostConfiguration config = new JobHostConfiguration(); config.NameResolver = new QueueNameResolver(); config.Queues.NewBatchThreshold = 10; JobHost host = new JobHost(config); host.RunAndBlock(); } public static void ExecuteStorageQueueItem([QueueTrigger("%AzureQueueName%")]

Deserializing ServiceBus content in Azure Logic App

由 时间秒杀一切 提交于 2019-12-07 02:09:21
问题 I'm trying to read the content body of a message in an Azure Logic App, but I'm not having much success. I have seen a lot of suggestions which say that the body is base64 encoded, and suggest using the following to decode: @{json(base64ToString(triggerBody()?['ContentData']))} The base64ToString(...) part is decoding the content into a string correctly, but the string appears to contain a prefix with some extra serialization information at the start: @string3http://schemas.microsoft.com/2003

C# communication between processes

由 左心房为你撑大大i 提交于 2019-12-07 00:59:10
问题 I'm working with an application, and I am able to make C# scripts to run in this environment. I can import DLLs of any kind into this environment. My problem is that I'd like to enable communication between these scripts. As the environment is controlled and I have no access to the source code of the application, I'm at a loss as to how to do this. Things I've tried: File I/O: Just writing the messages that I would like each to read in .txt files and having the other read it. Problem is that

Service Bus 1.0 for Windows Server Transaction/Error Handling

由 纵然是瞬间 提交于 2019-12-06 11:43:42
问题 I'm sure I'm not the first to say it, but there's a severe lack of documentation on the finer points of Service Bus 1.0 for Windows Server out there... I'm hoping some of the MS insiders can help clear a few things up... Do services utilizing queues/topics run in an implicit, ambient transaction? For instance consider the following code snippet: [ServiceBehavior] public class MySbService : IDoWork { [OperationBehavior] void DoSomeWork(WorkRequest request) { DoDatabaseWork();

ServiceBus throws 401 Unauthorized Error

由 限于喜欢 提交于 2019-12-06 09:30:06
I'm using a simple implementation of the Windows Service Bus 1.0 Brokered messaging to keep track of the user interactions with a particular web application. Every time something is saved to a "sensitive" table in the database, I have setup the repository layer send a message like so: ServiceBus.MessageQueue<T>.PushAsync(entity); which will then serialize the entity and create a message out of it. My MessageQueue class is something like this. public static class MessageQueue<T> { static string ServerFQDN; static int HttpPort = 9355; static int TcpPort = 9354; static string ServiceNamespace =

Microsoft Service Bus 1.0 unable to communicate with a server outside the client's domain

由 落爺英雄遲暮 提交于 2019-12-06 08:55:33
问题 I have installed Service Bus 1.0 on a server joined to a Domain. From a client app running on a PC joined on the same domain, I am able to create queues, messages, etc. I use a connection string specifying credentials of a user on the same domain. Everything works. From a client app running on a PC outside the domain, nothing works. I was thinking it was related to the fact that it was not possible to use a user from the server domain if the client app was not on the same domain, so I also

Sending 1000 brokered messages to the service bus using the SendBatchAsync method

由 徘徊边缘 提交于 2019-12-06 06:24:29
I have an application wherein data is fetched from the SQL DB and sent to the service bus as brokered message. These are the steps: Data fetched from the DB(in batches of 1000) Each row of data converted into Brokered Message and added into a list. The list of 1000 brokered messages is sent to the service bus using SendBatchAsync method. It is at the 3rd step that I am facing the issue. This is the code for that: public async Task SendMessagesAsync(List<BrokeredMessage> brokeredMessageList) { try { var topicClient = CreateTopicClient(); await topicClient.SendBatchAsync(brokeredMessageList); }

How to handle message order in nservicebus?

由 别等时光非礼了梦想. 提交于 2019-12-06 05:27:16
I'm trying to find a way to process messages in the order they were sent from the sender since NServiceBus does not guarantee that messages will be processed in a particular order. The sender is an order system which publishes createOrder and reviseOrder commands. The sender allows the user to submit multiple revisions to the same order so there can be revision 4 and revision 3 in the queue at the same time. Each revision has a revision number and reason code associated with it which drives some business logic so we cannot ignore any revisions or at least the reason part of it. A couple of
订阅 servicebus