azureservicebus

问题 This question already has answers here : Auto-expire orphaned Subscription (Azure ServiceBus Messaging SubscriptionClient) (3 answers) Closed 5 years ago . I create subscriptions per client instance and would like to understand good practices on cleaning up stale subscriptions if the client crashes or closes unexpectedly. Is there any way to determine by iterating through all the subscriptions of a topic to detect if the subscription hasn't been pulled for 24 hrs? I found Detect and Delete

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

问题 This question already has an answer here : Getting “amqp:internal-error” when peeking messages from Azure Service Bus Queue using AMQP, rhea and Node (1 answer) Closed 2 years ago . I'm trying to "Peek" messages from an Azure Service Bus queue using nodeamqp10 library but unfortunately I am not able to do so. Here's the code I am using: const AMQPClient = require('amqp10/lib').Client, Policy = require('amqp10/lib').Policy; const protocol = 'amqps'; const keyName = 'MyPolicy'; const sasKey =

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

问题 I am developing a solution which involves reading messages from an Azure service bus queue using the BizTalk SB-Messaging adapter. I am using the BizTalk Deployment Framework to deploy the application without user input. Some adapters have an option to acquire credentials for external systems using the Single Sign-On database (option 'Use SSO'). The SB-Messaging adapter doesn't have this feature, and requires that either ACS (Access Control Service) or SAS (Shared Access Secret) credentials

问题 We are using .Net framework 4.6.x and looking for a way to create an azure service bus namespace from the azure.management sdk. We are having trouble implementing programmatically within .Net with C#, Any reference or direct documentation would be helpful. The documentation on msdn seems to utilize the old REST api, we need to upgrade away from this now since windows has done the same. Any direction or references that do not create the service bus in the physical portal or use the REST api.

问题 From last question about Azure messaging service by publishing one common message to multiply subscribers by using service bus topic . But we've encounter an issue that our message size is over-sized of the service buss limitation(256KB), so we changed our design by splitting the GIANT message into small piece of sub-message and send them to different subscribers , here is what I'd like to achieve: Let's say we are saving an order object in azure function called SaveOrder and after order was

问题 What are the following open ports for on Azure Service Bus? 8443 (is this for the Management API?) 17000 17007 18000 18007 19000 19007 I can find documentation on other port such as 9350-9354, 5671, 5672, etc., but not ones on the list above. I need to document these for a penetration test on a project. Regards, Morten UPDATE: Below is a screenshot of the NMap scan of a Service Bus endpoint 回答1: Azure Service Bus is using two default ports: 443 (HTTPS) for management operations and fail-over

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