azureservicebus

问题 The challenge here is that I'm trying to create a single facade for dealing with queues and topics while maintaining semantics of Send vs. Publish For example: public interface IServiceBus { Task Send<T>(T message, string destination, SendOptions options = null); Task Publish<T>(T message, string topic, SendOptions options = null); } Send() would send a message to a queue and Publish() would publish a message to a topic. So I would need to have an instance of IQueueClient and ITopicClient to

问题 I'm sending messages through HTTP POST to my Azure Event Hub (to use with IoT Hub and a Blob storage). These are the HTTP call's settings: Every time I send a message, I get a request, but no message. I've tried: different SAS keys and owners different headers as well as no headers I've added the headers after finding this question. I also made sure to check the permissions, as it was suggested there, but they were already set to the necessary level. Noteworthy: for some reason, it did work

问题 As per this article: https://azure.microsoft.com/en..., Service Bus can process upto 2000 messages per second per queue/topic. This article: https://azure.microsoft.com/en... says 'This means that the overall throughput of a partitioned queue or topic is no longer limited by the performance of a single message broker or messaging store.' If we create a partitioned queue/topic, I believe it creates 16 partitions internally. My question is: Does the throughput of a partitioned queue/topic rise

问题 As per this article: https://azure.microsoft.com/en..., Service Bus can process upto 2000 messages per second per queue/topic. This article: https://azure.microsoft.com/en... says 'This means that the overall throughput of a partitioned queue or topic is no longer limited by the performance of a single message broker or messaging store.' If we create a partitioned queue/topic, I believe it creates 16 partitions internally. My question is: Does the throughput of a partitioned queue/topic rise

问题 I currently have an azure function using the ServiceBusTrigger binding [ServiceBusTrigger("%TopicName%", "%SubscripionName%", Connection = "MyConnection")] string catclogueEventMsgs, ILogger log, ExecutionContext context) which uses this local.settings.json file "Values": { … "MyConnection": "Endpoint=sb://testxxxxxxxxxxxxxxxxxx "SubscriptionName": "testsubscriptionName" "TopicName": "testtopicName", } How do I represent this in the appsettings.json file. Will it be like the below? "Values":

问题 I currently have an azure function using the ServiceBusTrigger binding [ServiceBusTrigger("%TopicName%", "%SubscripionName%", Connection = "MyConnection")] string catclogueEventMsgs, ILogger log, ExecutionContext context) which uses this local.settings.json file "Values": { … "MyConnection": "Endpoint=sb://testxxxxxxxxxxxxxxxxxx "SubscriptionName": "testsubscriptionName" "TopicName": "testtopicName", } How do I represent this in the appsettings.json file. Will it be like the below? "Values":

问题 I have an Azure function (based on the new C# functions instead of the old .csx functions) that is triggered whenever a message comes into an Azure Service Bus Queue. Once the function is triggered, it starts processing the service bus message. It decodes the message, reads a bunch of databases, updates a bunch of others, etc... This can take upwards of 30 minutes at times. Since, this is not a time sensitive process, 30 minutes or even 60 minutes is not an issue. The problem is that in the

问题 Im trying to trace and identify root cause for memory leak in our very small and simple Spring Boot application. It uses following: - Spring Boot 2.2.4 - azure-servicebus-jms-spring-boot-starter 2.2.1 - MSSQL Function: The app only dispatches Azure ServiceBus queue and stores data and sends data to other destination. It is a small app so it starts easily with 64 megs of memory, despite I give it up to 256 megs via Xmx option. Important note is the queue is being dispatched using Spring

问题 Im trying to trace and identify root cause for memory leak in our very small and simple Spring Boot application. It uses following: - Spring Boot 2.2.4 - azure-servicebus-jms-spring-boot-starter 2.2.1 - MSSQL Function: The app only dispatches Azure ServiceBus queue and stores data and sends data to other destination. It is a small app so it starts easily with 64 megs of memory, despite I give it up to 256 megs via Xmx option. Important note is the queue is being dispatched using Spring

问题 I want to use Azure Service Bus from inside an .NET Core 2.1 application. I'm familiar with the SDK coming with the Nuget package Microsoft.Azure.ServiceBus and using this I'm currently writing to a topic and receiving messages from there. What I want now is to create subscriptions on this topic for every client. The point is that I want to create a filtered subscription using the SqlFilter . This means, I have to create the subscription by code. BTW: As far as I've seen it the only other way