azure-storage-queues

问题 I want to be able to use Logic Apps to put/post messages in an Azure Storage Queue, because I want to make use of the Managed Identity option that HTTP Logic App acion provides. I have a Logic App that uses HTTP action to post XML messages to the queue and I have a "Put a message on a queue" action that puts JSON message to the queue for debugging purposes. My ultimate goal is to be able to use the HTTP action with Managed Identity as Authentication but be able to post JSON messages to the

问题 I'm receiving the following error when I try connecting to the emulated storage queue service: The MAC signature found in the HTTP request '...' is not the same as any computed signature. Make sure the value of Authorization header is formed correctly including the signature. This is the approach I'm using to connect to the azure storage: var storageAccount = 'devstoreaccount1' var accessKey= 'Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==' var azure

问题 I have a Storage Queue triggered Python Azure Function that submits a job to a third-party rate-limited API (1 request/minute). The queue that triggers the function will periodically receive a burst of messages, so I need a way to ensure that the function will be triggered immediately upon receiving the first message, 1 minute later on the second message, 2 minutes later on the third message, etc. until the queue is empty. Is it possible to either rate-limit the queue or the function so I am

问题 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 8 years ago . A delay queue is a queue in which each message has a delay time associated with it and a message can only be taken when its delay has expired. The head of the queue is that message whose delay expired furthest in

问题 I have an Azure Functions QueueTrigger that listens on a storage queue for messages like this: Message text -------------------------- {"ClientName": "client1"} {"ClientName": "client2"} {"ClientName": "client3"} The QueueTrigger then has code like this: if 'client1' == queue_msg['ClientName']: # do work required for client1 elif 'client2' == queue_msg['ClientName']: # do work required for client2 elif 'client3' == queue_msg['ClientName']: # do work required for client3 I'm using the Linux

问题 I have an Azure Functions QueueTrigger that listens on a storage queue for messages like this: Message text -------------------------- {"ClientName": "client1"} {"ClientName": "client2"} {"ClientName": "client3"} The QueueTrigger then has code like this: if 'client1' == queue_msg['ClientName']: # do work required for client1 elif 'client2' == queue_msg['ClientName']: # do work required for client2 elif 'client3' == queue_msg['ClientName']: # do work required for client3 I'm using the Linux

问题 If I were to get a message from queue using Azure.Storage.Queue queue.GetMessage(TimeSpan.FromMinutes(20)); I can set the visibility timeout, however when trying to use Azure.WebJobs (SDK 0.4.0-beta) attributes to auto bind a webjob to a queue i.e. public static void ProcessQueueMessage([QueueTrigger("myqueue")] string message){ //do something with queue item } Is there a way to set the visibility timeout on the attribute? There does not seem to be an option in JobHostConfiguration().Queues.

问题 I have successfully create a storage account on Azure with the following settings: Deployment: Resource manager Type: General Purpose (Standard) Replication: ZRS On the Azure portal I can see a "Blobs" service and if I click on it, I can create blob containers under the blob domain: https://[account_name].blob.core.windows.net/ So far so good. When I try to create a queue using the Azure SDK in a C# app I get the error that it can't find the domain for [account_name]. queue .core.windows.net

问题 Scenario: if I've spin off multiple Worker roles or ONE Worker role with multiple threads, which polls the new messages in Azure Queue. Could someone please confirm if the this the correct design approach? The reason I would like to have many worker roles is to speed up the PROCESSJOB. Our application should be near real time, i.e. as soon as there are messages we should get, apply complex business rules and commit to AZURE DB. We are expecting 11,000 message per 3min. Thank you. 回答1: You may

问题 I need to generate quite a number of reports and a report can take about 5 minutes to be generated, large amount of data, many different sources. The client will post messages to an Azure Storage Queue. There is a worker roles that processes the messages and generates the reports. If I want to scale this up let's say I end up with 10 worker roles that will process the messages from the queue and generate the reports. Then I will add messages into the queue like this: message 1: process