brokeredmessage

来源： https://stackoverflow.com/questions/62940422/are-net-standard-messages-effectively-incompatible-with-net-framework-brokered

问题 So I have an azure function acting as a queue trigger that calls an internally hosted API. There doesn't seem to be a definitive answer online on how to handle a message that could not be processed due to issues other than being poisonous. An example: My message is received and the function attempts to call the API. The message payload is correct and could be handled however the API/service is down for whatever reason (this time will likely be upwards of 10 minutes). Currently what happens is

问题 I've got a BrokeredMessageContext class which uses a Timer to periodically check and renew the lock on a BrokeredMessage instance in case the process that handles this message runs for longer than expected. It renews the lock by calling the RenewLock() method on the BrokeredMessage instance. I expected this call to give me a new lock with the same timeout as the original lock (MSDN states that "You can renew locks for the same duration as the entity lock timeout, and there is no maximum

问题 I have an application wherein data is fetched from the SQL DB and sent to the service bus as brokered message. These are the steps: Data fetched from the DB(in batches of 1000) Each row of data converted into Brokered Message and added into a list. The list of 1000 brokered messages is sent to the service bus using SendBatchAsync method. It is at the 3rd step that I am facing the issue. This is the code for that: public async Task SendMessagesAsync(List<BrokeredMessage> brokeredMessageList) {

问题 I have an application wherein data is fetched from the SQL DB and sent to the service bus as brokered message. These are the steps: Data fetched from the DB(in batches of 1000) Each row of data converted into Brokered Message and added into a list. The list of 1000 brokered messages is sent to the service bus using SendBatchAsync method. It is at the 3rd step that I am facing the issue. This is the code for that: public async Task SendMessagesAsync(List<BrokeredMessage> brokeredMessageList) {

问题 I have created an azure service bus topic application which peek all messages in deadletter . Some specific messages(with particular messageid) which i peeked need to be removed from the deadletter queue. Please provide help for implementing this. 回答1: By calling complete on the reference to the brokered message you receive from the dead letter queue you can remove it from the dead letter queue. https://msdn.microsoft.com/library/azure/microsoft.servicebus.messaging.brokeredmessage.complete

问题 Hi i was wondering why i get a special namespace in my brokered message content from my service bus when i fetch the message from the topic. and how do i remove it? i have my xml, and when i (in my Azure function) try to retrieve the message from the service bus i get this on top of everything or better said before my root node: @string3http://schemas.microsoft.com/2003/10/Serialization/�� <rootNode>...</rootNode> when i retrieve the brokered message from my servicebus in my azure function i

问题 I have created an instance of a BrokeredMessage and want to test my code around it's deliverycount versus a queue's max delivery count. I don't want to standup a real queue to send and receive the message on, but the deliverycount property is not initialized until the message is delivered. How can I fake this? 回答1: the deliverycount property is not initialized until the message is delivered. How can I fake this? BrokeredMessage.DeliveryCount property is read-only, and the value of

问题 I am working with Azure Service Bus Topics and Subscriptions. It's being used to send control messages across the application. The message listeners (subscribers) are running in a worker role and they are picking up the messages and processing the request. Each message in the bus can be picked up by only once, even if there are multiple listeners running simultaneously. There is no issue in using the Service Bus; however we are facing some issues while debugging/testing the application in

问题 I am testing a project with a dead letter queue with Microsoft Service Bus. I send 26 messages (representing the alphabet) and I use a program that when receiving the messages, randomly puts some of them in a dead letter queue. The messages are always read in peek mode from the dead letter queue, so once they reach there they stay there. After running a few times, all 26 messages will be in the dead letter queue, and always remain there. However, when reading them, sometimes only a few (e.g.