azureservicebus

问题 I'm trying to route messages from an IoT hub to a function app using a service bus queue as an Iot hub endpoint. The messages I send to the IoT hub are registered in the IoT hub, but won't be routed to the service bus queue. When I monitor the service bus queue, I only see successful requests. I implemented two routing rules with the following criteria: $._eventtype="meeting" and $body._eventtype="meeting" I tested the second one with the example provided by Azure and it matched. Neither of

问题 I want to set the messaging unit of premium service bus to 4 via PowerShell 5. Using following command: New-AzureRmServiceBusNamespace -ResourceGroup Default-ServiceBus-NorthEurope ` -Location NorthEurope -NamespaceName #{PremiumServiceBus} -SkuName "Premium" ` -Capacity 4 It gives capacity is unrecognized variable. What to do? 回答1: Capacity parameter is not defined by the Powershlell cmdlet (see documentation). This is possible using REST API. Looks like a disconnect between the PS library

问题 In Azure Service Bus, if below is the sequence of events, then all's fine - Create Topic Create Subscriptions inside Topic Send Messages to Topic With above, the subscriptions are triggered when a message is sent. This is expected. However, if we modify the above sequence like this Create Topic Send Messages to Topic Create Subscriptions inside Topic In this case, as messages are sent to a topic whilst no subscriptions were in place, when the subscriptions are indeed created, the previously

问题 I'm trying to understand the retry policy on the Azure Service Bus but it's not working the way I would expect. I have the following code that both listens for messages and sends a message to a specific azure queue. using System; using Microsoft.ServiceBus; using Microsoft.ServiceBus.Messaging; namespace ServiceBusTester { class Program { static void Main(string[] args) { var connectionString = "Endpoint=sb://<NamespaceName>.servicebus.windows.net/;SharedAccessKeyName

问题 We are using the Microsoft Azure Service Bus to send command messages and we are using the OnMessage approach to get them from the bus. Inside of our implementation of IMessageSessionAsyncHandler.OnMessageAsync, it can be that we realize that a message is not ready for processing. So I want to get the message from the bus and readd them to the end of the queue . The get/readd operations must be atomic. How can I achieve this? Thats my current solution (highly abstracted) but I am afraid about

问题 We are using the Azure Service Bus Relay for connecting our on-premise WCF services to our Azure-hosted Web Role. When we upgrade our on-premise WCF services, we always get a 502 Bad Gateway response from our first few requests through the Azure Service Bus, after the service bus host has re-established itself with the relay ( we don't get the "No service is hosted at the specified address." since the service is hosted properly). After a given timeout period - it seems the error disappears

问题 I have successfully tested an azure apns hub in sandbox mode. Now when I try to switch over to production, nothing works. I have read the tutorials, and i'm sure that I generated the production certificate right. Does anybody have an idea what the problem would be? At some point I think I have read that while I was using an Iphone to test the sandbox apns, it may not work after switching to production. 回答1: After debugging some more, I figured out what the problem was. I had to run my

问题 I am trying to implement Retry Policy for Service Bus transient error. I want my system to try exponentially like 1s, 2s, 4s, 8s, 16s, 32s, 64s, 128s. private int minBackoffDelayInMilliseconds = 2000; private int maxBackoffDelayInMilliseconds = 10000; private int deltaBackoffInMilliseconds = 2000; var defaultPolicy = new RetryPolicy<ServiceBusTransientErrorDetectionStrategy>(new ExponentialBackoff(maxRetries, TimeSpan.FromMilliseconds(minBackoffDelayInMilliseconds), TimeSpan.FromMilliseconds

问题 I'm working with a Service Bus queue triggered function. When we manually ( and crucially immediately ) DeadLetter the BrokeredMessage, it does indeed go to the dead letter queue. However, the runtime reports the following error: The lock supplied is invalid. Either the lock expired, or the message has already been removed from the queue Example function: [FunctionName("MySbFunction")] public static async Task Run( [ServiceBusTrigger("topic-name", "subscription-name", AccessRights.Manage,

问题 Basically, within an Azure Service Bus, I have a topic and a subscription. If a message arrives in the topic between 11:00AM, my subscriber should not handle it yet. However, at 14:00PM, I would expect my subscriber to treat it. Is there a way to achieve this natively with Topic filters? I don't find any mention of this kind of use case in the official documentation regarding filters. Indeed, all presented samples are about: " subscriber handling this kind of message, or never ". I'm looking