Question

我正在从工作者角色向服务总线队列发送消息。我注意到随机丢失了一些消息。

当我调试时，我在Send方法之后设置一个断点并登录到我的Azure Panel以检查消息队列是否增加。我发现的是奇怪的是，消息有时候不会添加到队列中。但它不是随机的。模式是：正确添加一条消息，下一条消息丢失，然后下一条消息正常，下一条消息丢失。

我已经实现了如下所示的重试模式，但显然并非所有消息都正确发送。

我的代码是：

var baseAddress = RoleEnvironment.GetConfigurationSettingValue("namespaceAddress");
var issuerName = RoleEnvironment.GetConfigurationSettingValue("issuerName");
var issuerKey = RoleEnvironment.GetConfigurationSettingValue("issuerKey");
var retryStrategy = new FixedInterval(5, TimeSpan.FromSeconds(2));
var retryPolicy = new RetryPolicy<ServiceBusTransientErrorDetectionStrategy>(retryStrategy);
Uri namespaceAddress = ServiceBusEnvironment.CreateServiceUri("sb", baseAddress, string.Empty);

this.namespaceManager = new NamespaceManager(namespaceAddress, TokenProvider.CreateSharedSecretTokenProvider(issuerName, issuerKey));
this.messagingFactory = MessagingFactory.Create(namespaceAddress, TokenProvider.CreateSharedSecretTokenProvider(issuerName, issuerKey));
//namespaceManager.GetQueue("chatmessage");
QueueClient client = messagingFactory.CreateQueueClient("chatmessage");
APPService.Model.MessageReceived messageReceived = new Model.MessageReceived();
messageReceived.From= e.From;
messageReceived.Op = e.Operator;
messageReceived.Message = e.Body;
BrokeredMessage msg = null;

// Use a retry policy to execute the Send action in an asynchronous and reliable fashion.
retryPolicy.ExecuteAction
(
    (cb) =>
    {
        // A new BrokeredMessage instance must be created each time we send it. Reusing the original BrokeredMessage instance may not 
        // work as the state of its BodyStream cannot be guaranteed to be readable from the beginning.
        msg = new BrokeredMessage(messageReceived);

        // Send the event asynchronously.
        client.BeginSend(msg, cb, null);
    },
    (ar) =>
    {
        try
        {
            // Complete the asynchronous operation. This may throw an exception that will be handled internally by the retry policy.
            client.EndSend(ar);
        }
        finally
        {
            // Ensure that any resources allocated by a BrokeredMessage instance are released.
            if (msg != null)
            {
                msg.Dispose();
                msg = null;
            }
        }
    },
    ()=>{},
    (ex) =>
    {
        // Always dispose the BrokeredMessage instance even if the send operation has completed unsuccessfully.
        if (msg != null)
        {
            msg.Dispose();
            msg = null;
        }

        // Always log exceptions.
        Trace.TraceError(ex.Message);
    }
);

可能出现什么问题？

Answer 1

只是查看您的代码，我无法注意到云导致问题的任何问题。我想门户网站上的计数器没有实时更新，所以我不认为它是一个测试结果。

我知道我现在没有帮助，但如果我怀疑你在表达，我会建立一个端到端的测试来发送和接收消息，比较messageId。

您是否已在MSDN上使用Paolo Salvatori的Service Bus Explorer？您可以使用它来测试实体。它是探索和测试Service Bus的可靠工具。

Azure Service Bus队列：未发送消息

1 个答案: