azureservicebus

问题 I have a webjob app to process a ServiceBus queue, which runs fine, with the following method: public static void ProcessQueueMessage([ServiceBusTrigger("myQueueName")] BrokeredMessage message, TextWriter log) However, I would like to be able to change the queue name without recompiling, according for example to a configuration appsetting, can it be done? 回答1: I've found an implementation of the INameResolver using configuration setting from the azure-webjobs-sdk-samples. /// <summary> ///

问题 I have a client written for some time ago that uses the old library and does call GetBody<string>() to read the body when receiving messages. Now I have the new client Microsoft.Azure.ServiceBus (sends messages) that as far as I understand always uses Stream . So the old client just crashes as it expects string body type. I have found a lot of information on the opposite scenario (new reader, old writer), but cannot figure out how to make the new client send the data in required format.

问题 I am using the Window Server Service Bus 1.1. I am able to generate the OAuth token from the Window Server Service Bus using the following base address string baseAddressHttp = "https://" + ServerName + ":9355/" + Namespace + "/$STS/OAuth/"; For Window Azure Service Bus for sending a message to queue i can POST a request on the following queue address string serviceNamespace = "ServiceBusDefaultNamespace"; string queueName = "SampleQueuName"; string message ="This is my first message"; string

问题 I'm receiving events from an EventHub using EventProcessorHost and an IEventProcessor class (call it: MyEventProcessor). I scale this out to two servers by running my EPH on both servers, and having them connect to the Hub using the same ConsumerGroup, but unique hostName's (using the machine name). The problem is: at random hours of the day/night, the app logs this: Exception information: Exception type: ReceiverDisconnectedException Exception message: New receiver with higher epoch of '186'

问题 We have created a downloading client-service model application in which a WCF service is hosted on one of our servers and the client application is distributed among the partners. Partners are provided with unique pin using which they can authenticate themselves with the WCF service and can place requests for downloading to the WCF Service. The clients connect to the WCF Service through Windows Azure Service Bus within which we have created a namespace using which client applications can

问题 I'm aware of a similar post here but don't have enough rep to comment and ask for clarification. I've been trying to achieve a similar thing as the accepted answer suggests, with one service on Azure Service Bus capturing all Fault events, but can't see any events of type Fault being published. This is how I'm subscribed: Bus.Factory.CreateUsingAzureServiceBus( sbc => { var host = ConfigureServiceBus(serviceBusPath, sbc); sbc.SubscriptionEndpoint<Fault>(host, subscriptionName, ec => { ec

问题 In my python application, if any bad/good event happens, I want to send the event details as notification message to user's email addresses or phone #s that have been subscribed to this application. So I am looking for publisher-subscriber model azure cloud Looks like multiple Azure services achieving similar goal but having a thin line of differences. Event hubs and notification hubs seems promising. So my question is as follows: Can email ID/phone # be subscribed to Azure event hub and

问题 I am in the early stages of designing the high-level structure of how two of our enterprise applications will broadcast to topics in the Azure Service Bus. I am a novice user of this technology, and after my preliminary reading of the documentation, I am tempted to use a simple solution: use a separate topic for each different event type that we want to broadcast. I favor this solution (over using filters) since it provides the most granular control over shared access keys, the least amount

问题 If I schedule a message in the future using something like this: d = datetime.utcnow() + timedelta(minutes=5) task = {"some": "object"} sbs.send_queue_message( qn, Message( task, broker_properties={'ScheduledEnqueueTimeUtc': d} ) ) Then is there a way that I can view/delete messages that have been scheduled? send_queue_message doesn't return anything, and receive_queue_message understandably doesn't return items that are scheduled to be queued later - so I can't get hold of it to pass to

问题 I'm fairly new to using the servicebus and other Azure features. After creating a servicebus manually on the Azure portal, I try to figure out how this can be achieved automatically. After a while of reading I thought that using the azure resource manager should be the way to go. Deploying just one topic is no big deal. But I can't find an example, that shows how to deploy multiple topics and queues at once. Or am I on the wrong approach? Thanks for your answers! Helmut 回答1: What we do (and I