azureservicebus

问题 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) {

问题 I'm currently running Windows Service Bus 1.1 via Azure Pack. This versions official support life ended Jan 2018, I need a long term on-premises Service Bus option. Is Azure Service Bus available via the Azure Stack? Also looking for any recommended alternatives. Thanks re: https://azure.microsoft.com/en-us/blog/collaboration-and-federation-azure-service-bus-messaging-on-premises-futures/ 回答1: Short answer is "no". Azure Service Bus is planned for Azure Stack, but is not available today.

问题 I have a long running process which performs matches between millions of records I call this code using a Service Bus, However when my process passes the 5 minute limit Azure starts processing the already processed records from the start again. How can I avoid this Here is my code: private static async Task ProcessMessagesAsync(Message message, CancellationToken token) { long receivedMessageTrasactionId = 0; try { IQueueClient queueClient = new QueueClient(serviceBusConnectionString,

问题 I have a long running process which performs matches between millions of records I call this code using a Service Bus, However when my process passes the 5 minute limit Azure starts processing the already processed records from the start again. How can I avoid this Here is my code: private static async Task ProcessMessagesAsync(Message message, CancellationToken token) { long receivedMessageTrasactionId = 0; try { IQueueClient queueClient = new QueueClient(serviceBusConnectionString,

问题 I have an Azure Function triggered by Azure Service Bus queue - Azure Function App is hosted in consumption plan. How long does it take at most to wake up an Azure Function when new message in queue appears? (assuming there were no message during past 20 minutes). Is it specified anywhere? I've found in the Documentation that: For non-HTTP triggers, new instances will only be allocated at most once every 30 seconds. Does it mean that I won't be able to process the first message in the queue

问题 I've been reading on the Event-Driven Message Programming Model introduced in April 2013, the OnMessageOptions.ExceptionReceived Event, the built-in RetryPolicy (May 2013, RetryPolicy.Default), The Transient Fault Handling Application Block (2011) which is outdated, and more (see bottom). I've been monitoring the exceptions received through the message pump for transient errors and I get daily MessagingCommunicationExceptions . This article (Updated: September 16, 2014), recommend the

问题 I've tried to do my homework on this issue but no searches I can make have gotten me closer to the answer. Closest hit was Detect and Delete Orphaned Queues, Topics, or Subscriptions on Azure Service Bus. My scenario: I have multiple services running (standard win service). At startup these processes starts to subscribe to a given topic in Azure Service Bus. Let's call the topic "Messages". When the service is shut down it unsubcribes in a nice way. But sometimes stuff happens and the service

问题 I've been dealing with a spate of Timeout's from TopicClient and I think it may be related to object lifetime and disposal. I'm using the TopicClient class from Microsoft.ServiceBus.Messaging and reading this Best Practices Guide states You should not close messaging factories or queue, topic, and subscription clients after you send a message, and then re-create them when you send the next message. Closing a messaging factory deletes the connection to the Service Bus service, and a new

问题 I'm trying to set metadata for service bus messages in a JavaScript Azure Function using the service bus binding output. Unfortunately, it appears that the binding only supports the body. Looking at the docs, I see that you can access this information in service bus triggers via context.bindingData but I don't see any corresponding interface for service bus output. Is there some way to send a full brokered message and set the message properties (ContentType) and message custom properties ?

问题 We have an API hosted on Windows Azure in a web role with 2 instances that takes in requests, validates them then adds them to an Azure Service Bus Queue. Recently we've started load testing this and found that our current code throws the below exception: Could not add command to the command queue Exception: Microsoft.ServiceBus.Messaging.QuotaExceededException: The number of maximumallowed connections have been reached or exceeded for Queue Number of active connections: 100, Maximum allowed