servicebus

来源： https://stackoverflow.com/questions/26298271/problems-with-transactionscope-and-servicebus-in-production-environment

问题 Have developed an Azure service bus message receiver console app which is working fine console app. Code for console app as follows: using System.IO; using Microsoft.ServiceBus.Messaging; class Program { static void Main(string[] args) { const string connectionString = "Endpoint=sb://sbusnsXXXX.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=bkjk3Qo5QFoILlnay44ptlukJqncoRUaAfR+KtZp6Vo="; const string queueName = "bewtstest1"; var queueClient = QueueClient

问题 Is there a way to use SAS authentication for Azure ServiceBus in Azure Node.js SDK? Their home page still suggests using AZURE_SERVICEBUS_NAMESPACE and the AZURE_SERVICEBUS_ACCESS_KEY environment variables, which is the default user with all rights. 回答1: Connection strings is the way to go: var serviceBusService = azure.createServiceBusService('Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=DefaultListenSharedAccessSignature;SharedAccessKey=mysharedkey') Hope it helps,

问题 Using Azure SDK 2.3 on my vs2013 development VM I can consume Service Bus queues hosted in Azure painlessly. However, on Windows Server 2008 R2 Standard SP1, it looks like Windows can not trust the involved certificates and an exception is thrown. The line that throws : // Send the message await queueclient.SendAsync(message); Exception message : The X.509 certificate CN=servicebus.windows.net is not in the trusted people store. The X.509 certificate CN=servicebus.windows.net chain building

问题 Is there a way to log access to Azure Service Bus? We are looking for a way to log who create/delete a topic/subscription/namespace in Service Bus, either from Azure portal or from an external source like an API or Service Bus Explorer. We have Azure Activity Log, but it doesn't give a solution for external sources. We also checked Azure Diagnostic Logs, it doesn't help either. 回答1: Azure Service Bus .NET client allows diagnostics logging, you will have to enalbe diagnostics it first. That

问题 Is there a way to log access to Azure Service Bus? We are looking for a way to log who create/delete a topic/subscription/namespace in Service Bus, either from Azure portal or from an external source like an API or Service Bus Explorer. We have Azure Activity Log, but it doesn't give a solution for external sources. We also checked Azure Diagnostic Logs, it doesn't help either. 回答1: Azure Service Bus .NET client allows diagnostics logging, you will have to enalbe diagnostics it first. That

问题 If it supports, is the API exactly similar to the public cloud based Azure Servicebus. 回答1: No it does not. Relay is scheduled for a later release. That's why we call this release "Service Bus messaging engine" in the fine print. Clemens 回答2: Just Came to know, the upcoming AzurePack includes this feature. 来源： https://stackoverflow.com/questions/11644262/does-service-bus-for-windows-server-service-bus-1-0-beta-support-relay-functio

问题 I'm trying to disable HTTP keep-alive , and I can't seem to find any documentation on how to achieve that. Ultimately, I am occasionally getting: System.ServiceModel.CommunicationException : The underlying connection was closed: A connection that was expected to be kept alive was closed by the server I've heard the best approach is simply to disable HTTP keep-alive . 回答1: Ultimately I solved my own issue here with a little helper function that takes my basicHttpRelayBinding and modifies it

问题 I am trying to understand how can I make Azure Service Bus Topic to be scaleable to handle >10,000 requests/second from more than 50 different clients. I found this article at Microsoft - http://msdn.microsoft.com/en-us/library/windowsazure/hh528527.aspx. This provides lot of good input to scale azure service bus like creating multiple message factories, sending and receiving asynchronously, doing batch send/receive. But all these input are from the publisher and subscriber client perspective

问题 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.