azureservicebus

问题 How do you get the count of dead letter messages in an Azure Service Bus queue? I can get the count in the queue like so ... var ns = NamespaceManager.CreateFromConnectionString(sbConnectionString); var queue = ns.GetQueue(queueName); var count = queue.MessageCount; But this looks to include both messages in the queue, and also messages in the associated dead letter queue How can I differentiate between them? 回答1: Do take a look at MessageCountDetails property in QueueDescription. You will

问题 I'm involved in a multi-tier project, one part of which is consuming a stream of "events" from a third-party system. The vendor is publishing these via an Azure Service Bus Topic - they provide, control & manage the Bus. We are simply provided with the URI, TopicName and Subscription details. Our approach was to put together a Webjob, using the provided ServiceBusTrigger in the SDK to handle listening for new messages & triggering processing them into our system. However, we seem to have hit

问题 I have built a simple Chat application using SignalR followed the tutorial there, which works great. Then I followed the tutorial of SignalR Scaleout with Azure Service Bus, also from Microsoft. So I have completed all the following steps: Created a new Cloud Service on Azure Portal Created a new Service Bus namespace on Azure Portal Created a Windows Azure Cloud Service with a SignalR ASP.NET Web Role Setup the SignalR Web Role running on 2 instances (VM Size: Small) Deployed the Cloud

问题 I need to get a message from queue in some special time. So I use scheduled message in queue. I send messages via ScheduleMessageAsync method. For getting messages I use Azure Web Job with ServiceBusTrigger. I send a couple of messages, everything works fine on my side, but in Azure Portal, if I go to page with my queue I see that I have negative amount of messages in queue. I had this problem some days ago, but then it disappeared, but now appears again. Is it problem in my logic or just a

问题 I am starting work on a new project using the new Windows Server Service Bus 1.0 Beta. I am trying to set up a test environment on an AWS EC2 virtual machine. I have installed the Service Bus on a Windows Server 2008 R2 instance running on AWS EC2 and setup a new Farm, Container and Host according to the examples in the MSDN documentatoin. I have all of the proper ports open on the server (4443 and 9354). I also followed the instructions from [this page][1] to export the self generated

问题 In Microsoft Azure, under service bus, you can see activity graphs for the different queues/topics etc. The graph shows various different lines, such as incoming messages , outgoing messages , successful requests etc. What is a Request ? And what is a Message ? Requests seem to be constantly occurring and often significantly large than the number of messages (in topics). Even though the number of servers listening to the queue remains the same - sometimes the number of requests will

问题 I'm using MassTransit as my messaging framework, running on top of Azure Service Bus. I'm running MassTransit from inside a WebJob (although I don't think that matters) Now I'm trying to get MassTransit to process multiple messages at the same time, as I'm now dealing with messages that individually take a while to process. So to speed up performance, I don't want each message to be processed one by one. I tried setting MaxConcurrentCalls to , for example, 30, but that doesn't seem to do it.

问题 I know that error message is self-explanatory, we can't read message body multiple times. here I'm using AOP (Aspect Oriented Programming) for audit log. [AuditServiceMethod(AttributePriority = 0)] [FunctionName("ValidateSubscriber")] public static async Task RunAsync([ServiceBusTrigger("validate-message", AccessRights.Manage, Connection = "ServiceBusConnection")]BrokeredMessage message, TraceWriter log, [Inject(typeof(ICommonUtilities))] ICommonUtilities commonUtility) { string body; using

问题 I am going through an effort to upgrade code that used the old Windows Azure Service Bus (pre 2.0). This code based used the Enterprise Library Transient Fault Handling blocks to provide a retry policy that is leveraged when calling into the Service Bus API to send and receive queue messages. Typically the code would look like this (minus all the try/catch/finally, etc.): retryPolicy.Execute(() => { queueClient.Send(msg); }); However, in Service Bus 2.0, retry policy is built into the

问题 The documentation of Service Fabric recommends service remoting, ICommunicationClient or WcfCommunicationClient to realize the communication between the micro services. The ServiceBus, which I always used for inter-service communication, is not even mentioned. Why? 回答1: I think you misinterpreted the docs. It does not recommend any protocol or service (the word is not even present on the page). What it does do is list the built-in communication options and appropriate situations of when to