azureservicebus

I am trying to connect Azure service bus from Java client with AMQP protocol I follow the instruction in the following link: http://azure.microsoft.com/en-us/documentation/articles/service-bus-java-how-to-use-jms-api-amqp/ 1) created service bus in Azure portal with the name space ' availo ' and a queue named ' queue1 ' 2) from service bus connection information I've got the following: SharedAccessKeyName=RootManageSharedAccessKey SharedAccessKey={key} 3) created "servicebus.properties" file for the JNDI lookup connectionfactory.SBCF = amqps://RootManageSharedAccessKey:encoded(key)@availo

So I'm trying the Notification Hubs on Azure. I have set things up according to this blog post . I have done the GCM setup in my Android code so I have a valid regId: String connectionString = "Endpoint=sb://<MYNAMESPACE>.servicebus.windows.net/;SharedAccessKeyName=DefaultListenSharedAccessSignature;SharedAccessKey=<MYKEY>"; hub = new NotificationHub("<MYHUB>", connectionString, this); hub.register(regid, "myTag"); So I get: com.microsoft.windowsazure.messaging.NotificationHubUnauthorizedException: Unauthorized on the hub.register method call. Any ideas? Unfortunately there is a bug in the

Is there such a thing as a ServiceBus provider? As part of my application I would like to include a SB namespace, topic and subscriptions. Is the expectation that you deploy the website(s) using ARM, and use the service interface for scripting the other supporting features? There is a Service Bus Provider now. Sample template: { "apiVersion": "2014-09-01", "name": "[parameters('namespace')]", "type": "Microsoft.ServiceBus/namespaces", "location": "[parameters('resourceLacation')]", "properties": { "messagingSku": "1", //basic tier "enabled": true, "status": "Active", "namespaceType":

I asked the very same question few days ago: Unable to "Peek" messages from an Azure Service Bus Queue using AMQP and Node . I'm asking the same question again but with a few differences (hence, please don't mark this question as a duplicate of the other question): In the previous question, I was using nodeamqp10 library however based on some comments on the Github page for this library, I ended up using rhea instead of nodeamqp10 library. With some help from Azure Service Bus team, I made some progress and now I am getting an error back from Azure Service Bus which tells me that I am on the

I've been looking into Azure Service Bus Queues ( NOT Azure Storage Queues). All of the details that I have read indicate that it supports FIFO semantics , but only in the context of a "Messaging Session". The problem is that I can't seem to find any information on what exactly this is in the context of Azure. Is this a WCF construct, or something that is particular to Azure Service Bus? I assume that it does not relate to local transactions, but I am not 100% sure. Any pointers would be very helpful. Thanks! Jim O'Neil Specifically it refers to MessageSession , and it's the

I recently created some partitioned queues from where I send and receive all the time. They've run as non-partitioned in the past without any of my current issues. The problem is, I have a constant number of messages in the queue that I can not receive. I always get nothing back when not sending any other messages to the queues but when I send messages to the queues I receive the new messages without a problem. The messages that are stuck in the queue are active messages, not dead lettered. I'm suspecting they're stuck in a specific partition(s) but I don't know how to receive them. Since I

We are using a service bus queue in our project. We are in need of a functionality to remove all the messages from the queue when the administrator chooses to clear the queue. I searched on the net but could not find any function which does this inside the QueueClient class. Do I have to pop all the messages one by one and then marking them complete to clear the queue or is there a better way? QueueClient queueClient = _messagingFactory.CreateQueueClient( queueName, ReceiveMode.PeekLock); BrokeredMessage brokeredMessage = queueClient.Receive(); while (brokeredMessage != null ) {