WildFly消息配置用于消息重试控制。

huangapple go评论54阅读模式
英文:

WildFly Messaging Configuration For Message Retry Control

问题

我们正在集群中运行 WildFly 26,并观察当出现异常时 JMS 消息的自动重试。一切都按预期运行,消息在多次尝试之间有短暂的延迟。

但是,我们想要限制重试的次数,而不是使用默认值,似乎默认值是 10 次。我唯一看到允许设置最大重试次数的地方在 JMS Bridge 中。有关 JMS Bridge 的讨论和示例是用于连接到外部的 JMS 子系统。我该如何配置 WildFly 以限制重试次数?

英文:

We are running WildFly 26 in a cluster and observe the automatic retry of JMS message when exception is thrown. All is working as expected where the message retries multiple times with a small delay between attempts.

However, we would like to limit the # retries instead of using the default which appears to be 10. The only place I have seen that allows you to set max-retries is in the JMS Bridge. The discussion and examples for JMS Bridge is for connecting to an external JMS subsystem. How do I configure WildFly to limit the number of retries ?

答案1

得分: 2

<address-setting name="jms.queue.MyQueue" max-delivery-attempts="10"/>

如果你想应用于 所有 地址,请使用 name="#"。默认的 standalone-full.xml 已经有一个这样的 address-setting,你可以修改它。

英文:

You can set the max-delivery-attempts in an address-setting with an appropriate name value, e.g.:

<address-setting name="jms.queue.MyQueue" max-delivery-attempts="10"/>

If you want this to apply to all addresses then use name="#". The default standalone-full.xml already has such an address-setting which you can modify.

huangapple
  • 本文由 发表于 2023年5月17日 21:03:22
  • 转载请务必保留本文链接:https://go.coder-hub.com/76272421.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定