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? I've found an implementation of the INameResolver using configuration setting from the azure-webjobs-sdk-samples . /// <summary> /// Resolves %name% variables in attribute values from the config file. /// </summary> public class

I am trying to improve throughput on a windows service using Azure Service Bus. What I have noticed is that if I have code like like this. client.OnMessageAsync(async message => { var timer = new Stopwatch(); timer.Start(); bool shouldAbandon = false; try { // asynchronouse processing of messages await messageProcessor.ProcessAsync(message); Interlocked.Increment(ref SimpleCounter); // complete if successful processing await message.CompleteAsync(); } catch (Exception ex) { shouldAbandon = true; Console.WriteLine(ex); } if (shouldAbandon) { await message.AbandonAsync(); } timer.Stop();

I have events of different types. For example, some data is telemetry data, some is error information etc. I thought it would be a good idea to create several IEventProcessor implementations, one for each event type. So each implementation will handle the event differently. Like writing to file or to database. What's the best way to route events to a specific EventProcessor? Should I let an EventProcessor monitor a specific partitionkey and if so, how? Should I use the constructor of the EventProcessorHost that lets me specify a consumergroupname? If so, how can I send to a specific

In Azure Service Bus, you can send a brokered message using QueueClient and MessageFactory . I would like to know why would you want to use one over the other. Azure Service Bus provides different way to send/receive messages. You can use the QueueClient to send and receive message to/from a queue. You can use the TopicClient to send message to a topic And you can use the SubscriptionClient to receive message from a subscription. Using MessageSender and MessageReceiver , you create sender and receiver that are entity type invariant: var factory = MessagingFactory.CreateFromConnectionString(

How is brokered messaging via Azure Service Bus done from a Xamarin Forms PCL...is there an SDK, library or plugin? If there is a way to hand roll a brokered message, I suppose it could be accomplished with an HttpClient & the REST API ... I finally have a working method for posting a message to an Azure Service Bus Queue from a Xamarin PCL! The way to do this is via an HttpClient. Gotchas that made the solution elusive: The nuget package for Microsoft.ServiceBus.Messaging will happily install, but has no exposure to the portable class. WebClient examples abound, but there is no webclient

I am using application(.Net Core) to send an object through azure service bus and received by a web job(.Net Core) Question is how to serialize/deserialize to send/receive the object? I found lots of reference for the legacy BroakerMessage.GetBody() to receive message, but not the new .Net Core method, please advice, thanks. Sender code: using Microsoft.Azure.ServiceBus; MyClass object = new MyClass(); var message = new Message(object); await queueClient.SendAsync(message); Receiver code: using Microsoft.Azure.ServiceBus; public void ProcessQueueMessage([ServiceBusTrigger("queue")] Message

Can someone offer some more guidance on the use of the Azure Service Bus OnMessageOptions.AutoRenewTimeout http://msdn.microsoft.com/en-us/library/microsoft.servicebus.messaging.onmessageoptions.autorenewtimeout.aspx as I haven't found much documentation on this option, and would like to know if this is the correct way to renew a message lock My use case: 1) Message Processing Queue has a Lock Duration of 5 minutes (The maximum allowed) 2) Message Processor using the OnMessageAsync message pump to read from the queue (with a ReceiveMode.PeekLock) The long running processing may take up to 10