使用AMQP,rhea和Node从Azure Service Bus Queue中查看消息时获取“amqp:internal-error”

问题描述 投票:1回答:1

几天前我问过同样的问题:Unable to "Peek" messages from an Azure Service Bus Queue using AMQP and Node。我再次提出同样的问题,但有一些差异(因此,请不要将此问题标记为另一个问题的副本):

  • 在上一个问题中,我使用的是nodeamqp10库,但是基于对该库的Github页面的一些评论,我最终使用rhea而不是nodeamqp10库。
  • 在Azure Service Bus团队的帮助下,我取得了一些进展,现在我从Azure Service Bus收到错误,告诉我我正在走上正轨。

这是我正在使用的新代码:

var client = require('rhea');
const keyName = 'MyCustomPolicy';
const sasKey = 'SAS Key'
const serviceBusHost = 'account.servicebus.windows.net';
const queueName = '003';

client.on('connection_open', (context) => {
  context.connection.open_sender({
    target: { address: `${queueName}/$management` }
  });
});

client.once('sendable', (context) => {
  console.log('messages can be sent now....');
  var receiver = context.connection.open_receiver({
    source: { address: `${queueName}/$management` },
    autoaccept: false,
    target: { address: 'receiver-link' }
  });

  receiver.once('receiver_open', (context) => {
    console.log('receiver is now open....');
  });

  receiver.once('message', (context) => {
    console.log('message received by receiver....');
    console.log(context.message);
  });

  var messageBody = {
    'from-sequence-number': 1,
    'message-count': 5
  };

  const msg = {
    application_properties: {
      operation: 'com.microsoft:peek-message'
    },
    body: client.types.wrap_map(messageBody),
    reply_to: 'receiver-link'
  };
  context.sender.send(msg);
  console.log('message sent....');
});

client.connect({
  transport: 'tls',
  host: serviceBusHost,
  hostname: serviceBusHost,
  username: keyName,
  password: sasKey,
  port: 5671,
  reconnect_limit: 10
});

现在,当我运行此代码时,我从Azure Service Bus收到500错误:

{
  "application_properties":
  {
    "statusCode":500,
    "errorCondition":"amqp:internal-error",
    "statusDescription":"The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:ab667ed6-1565-4728-97b7-6ae4a33468b9, TrackingId:538f93a1-2c07-4bc0-bf41-dc00d7ae963c_B13, SystemTracker:account-name:Queue:003, Timestamp:8/2/2018 7:43:52 AM",
    "com.microsoft:tracking-id":"538f93a1-2c07-4bc0-bf41-dc00d7ae963c_B13"
  }
}

我甚至检查了错误消息(http://go.microsoft.com/fwlink/?LinkId=761101)中包含的链接,但没有提到该链接上的amqp相关错误。

与前一个问题一样,如果我使用地址作为队列名称而不是queue-name/$management,我可以获取消息,但消息被锁定,消息的传递计数也在增加。此外,它返回队列中的所有消息,而不是我请求的5条消息。

我不确定我做错了什么。有人可以帮忙吗?

node.js azure amqp azureservicebus azure-servicebus-queues
1个回答
1
投票

在Azure Service Bus团队的帮助下,我找到了解决这个问题的方法(事实上,他们给了我这个解决方案)。基本上messageBody的元素应该使用AMQP类型正确编码。

以下代码有效:

  var messageBody = {
    'from-sequence-number': client.types.wrap_long(1),
    'message-count': client.types.wrap_int(5)
  };

  const msg = {
    application_properties: {
      operation: 'com.microsoft:peek-message'
    },
    body: messageBody,
    reply_to: 'receiver-link'
  };
© www.soinside.com 2019 - 2024. All rights reserved.