azureservicebus

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 following : This exception signals a communication error that can manifest itself when a connection from the

I want to use the Azure Service Bus REST API in JavaScript. Unfortunately I'm running into cross origin problems, as my Service Bus namespace is not in the same domain as my site. I know that you can enable CORS with many Azure services, but I can't find any resource in the Azure documentation or elsewhere telling me how to do this for the Service Bus. Does anybody know if, and how, this can be done? Blackhex I've solved this issue by creating a separate Web App with the following Web.config which is just a simple proxy. <?xml version="1.0" encoding="utf-8"?> <configuration> <system.webServer>

I'm dealing with a high throughput application of EventHub. According to the documentation , in order to achieve very high throughput from a single sender, then client-side batching is required (without exceeding the 256 KB limit per event). Best Practices for performance improvements using Service Bus brokered messaging suggests Client-side batching for achieving performance improvements. It describes client-side batching is available for queue or topic clients, which enables delaying the sending of messages for a certain period of time, then it transmits the messages in a single batch. Is

I am preparing to develop application that connects to Azure Service Bus. For development I want use Service Bus 1.1. I have installed localy Service Bus 1.1 and it works fine when I am connecting with package Service Bus.v1_1 ver. 1.0.5 . But as I want eventually work with Azure I prefer to use package WindowsAzure Service Bus which as I know sholud work with Service Bus 1.1. But when I want to execute: namespaceManager.QueueExists(queueName) with WindowsAzure.ServiceBus ver 3.1.2 package I receive: 'System.ArgumentException' .... The remote server returned an error: (400) Bad Request. The

I am new to Azure Service Bus and would like to know if I can multiple subscribers to a queue or topic? In rabbit MQ I can have multiple subscribers to 1 publisher. What I am trying to do is, I am using CQRS and when certain commands come into the system when the event is handled I want to push them into a message queue. I want 2 subscribers to be able to get the messages from that queue, one for me to process internally. another one for process and send externally. I am new to Azure Service Bus and would like to know if I can multiple subscribers to a queue or topic? Yes. This is possible

I got an exception of Microsoft.ServiceBus.Messaging.LeaseLostException, in my EventHub processor. what does this exception mean? What is the possible root cause of this exception? Following are stack track: at Microsoft.ServiceBus.Messaging.BlobLeaseManager.d__24.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.ServiceBus.Messaging.BlobLeaseManager.d__25

I have an svc that is auto-started using AppFabric. What I want to do is expose the wsdl for my service over the bus . Internally the service and the wsdl work fine of course, I can also consume the service over the bus with no issue. The only thing I can't configure properly is viewing the wsdl over the relay. The ServiceHostFactory creates default endpoints and also adds an Azure Endpoint along with a mex endpoint in hopes to expose the wsdl over the relay. When I try to view the wsdl from the service bus url, I get the mismatch fault, probably due to ACS authentication failing? ...cannot be

I have been using Azure Storage Queues to feed a WebJob, using the QueueTrigger attribute. I configure my QueueTrigger to dequeue a number of items for concurrent processing, like this: public static void Main() { JobHostConfiguration config = new JobHostConfiguration(); config.NameResolver = new QueueNameResolver(); config.Queues.NewBatchThreshold = 10; JobHost host = new JobHost(config); host.RunAndBlock(); } public static void ExecuteStorageQueueItem([QueueTrigger("%AzureQueueName%")] CloudQueueMessage message, TextWriter logger) { ProcessRequest(message.AsString, logger); } I would prefer