ActiveMQ-Artemis 2.6 使用JMS管理API设置队列死信地址答案

【问题标题】：ActiveMQ-Artemis 2.6 Set queue dead letter address using JMS management APIActiveMQ-Artemis 2.6 使用JMS管理API设置队列死信地址
【发布时间】：2018-07-24 06:17:07
【问题描述】：

我正在尝试通过 JMS 管理 API 为队列设置死信地址。从阅读最新的 Artemis 文档看来，我应该能够使用 QueueControl.setDeadLetterAddress(...) 方法来做到这一点。请参阅https://activemq.apache.org/artemis/docs/latest/management.html 并搜索“setDeadLetterAddress”。

据我了解，这些方法的参数应该在 Artemis QueueControl javadocs 中找到： https://activemq.apache.org/artemis/docs/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/QueueControl.html

但是，该文档没有提及 setDeadLetterAddress 方法或可能接受的参数。

QueueControl.setDeadLetterAddress 方法是否还存在，是否可以从 JMSManagementHelper.putOperationInvocation(...) 方法中调用？

非常感谢！

【问题讨论】：

标签： activemq-artemis

【解决方案1】：

查看QueueControlImpl 类代码，很明显 setDeadLetterAddress 操作不再存在。 ActiveMQServerControlImpl class 中名为 AddressSettings 的操作确实提供了为队列设置 DLA 的功能（以及许多其他设置）。

例如：

Queue managementQueue = ActiveMQJMSClient.createQueue("activemq.management");
Queue replyQueue = ActiveMQJMSClient.createQueue("management.reply");

JMSContext context = connectionFactory.createContext();
JMSConsumer consumer = context.createConsumer(replyQueue)) {
JMSProducer producer = context.createProducer();
producer.setJMSReplyTo(replyQueue);

// Using AddressSettings isn't required, but is provided
// for clarity.
AddressSettings settings = new AddressSettings()
        .setDeadLetterAddress(new SimpleString("my.messages.dla"))
        .setMaxDeliveryAttempts(5)
        .setExpiryAddress(new SimpleString("ExpiryAddress"))
        .setExpiryDelay(-1L) // No expiry
        .setLastValueQueue(false)
        .setMaxSizeBytes(-1) // No max
        .setPageSizeBytes(10485760)
        .setPageCacheMaxSize(5)
        .setRedeliveryDelay(500)
        .setRedeliveryMultiplier(1.5)
        .setMaxRedeliveryDelay(2000)
        .setRedistributionDelay(1000)
        .setSendToDLAOnNoRoute(true)
        .setAddressFullMessagePolicy(AddressFullMessagePolicy.PAGE)
        .setSlowConsumerThreshold(-1)  // No slow consumer checking
        .setSlowConsumerCheckPeriod(1000)
        .setSlowConsumerPolicy(SlowConsumerPolicy.NOTIFY)
        .setAutoCreateJmsQueues(true)
        .setAutoDeleteJmsQueues(false)
        .setAutoCreateJmsTopics(true)
        .setAutoDeleteJmsTopics(false)
        .setAutoCreateQueues(true)
        .setAutoDeleteQueues(false)
        .setAutoCreateAddresses(true)
        .setAutoDeleteAddresses(false);

Message m = context.createMessage();
JMSManagementHelper.putOperationInvocation(m, ResourceNames.BROKER, "addAddressSettings",
        "my.messages", 
        settings.getDeadLetterAddress().toString(),
        settings.getExpiryAddress().toString(),
        settings.getExpiryDelay(),
        settings.isLastValueQueue(),
        settings.getMaxDeliveryAttempts(),
        settings.getMaxSizeBytes(),
        settings.getPageSizeBytes(),
        settings.getPageCacheMaxSize(),
        settings.getRedeliveryDelay(),
        settings.getRedeliveryMultiplier(),
        settings.getMaxRedeliveryDelay(),
        settings.getRedistributionDelay(),
        settings.isSendToDLAOnNoRoute(),
        settings.getAddressFullMessagePolicy().toString(),
        settings.getSlowConsumerThreshold(),
        settings.getSlowConsumerCheckPeriod(),
        settings.getSlowConsumerPolicy().toString(),
        settings.isAutoCreateJmsQueues(),
        settings.isAutoDeleteJmsQueues(),
        settings.isAutoCreateJmsTopics(),
        settings.isAutoDeleteJmsTopics(),
        settings.isAutoCreateQueues(),
        settings.isAutoDeleteQueues(),
        settings.isAutoCreateAddresses(),
        settings.isAutoDeleteAddresses());
producer.send(managementQueue, m);

Message response = consumer.receive();
// addAddressSettings returns void but this will also return errors if the
// method or parameters are wrong.
log.info("addAddressSettings Reply: {}", JMSManagementHelper.getResult(response));

【讨论】：