Liberty 上的 JMS 激活规范:“WAS

本文介绍了Liberty 上的 JMS 激活规范:“WAS_EndpointInitialState"完整配置文件等效属性?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

限时送ChatGPT账号..

我们正在将一些应用从 WAS 完整配置文件迁移到 WAS Liberty 配置文件.
某些应用程序具有 MDB，并且需要连接到 MQ 的 JMS 激活规范定义.
为了对集群中的消息执行严格的 FIFO 排序，我们在这些激活规范上将 "WAS_EndpointInitialState" 属性设置为 "INACTIVE" 以告诉 WAS 完整配置文件不要启动启动时的激活规范.当集群启动时，我们仅在一台服务器上启动(即恢复")激活.
问:如何使用 Liberty (v16.0.x) 实现这一点?我在 "properties.wmqJms" 节中没有看到等效参数.
谢谢

We are migrating some apps from WAS full profile to WAS Liberty profile.
Some apps have MDBs and need JMS Activation Specs definitions connected to MQ.
In order to enforce strict FIFO ordering of messages in a cluster, we set the "WAS_EndpointInitialState" property to "INACTIVE" on those Activation Specs to tell WAS full profile to not start the Activation Spec on startup. When the cluster starts, we start (ie "resume") the activation on one server only.
Q: How to achieve this with Liberty (v16.0.x) ? I don't see an equivalent parameter within the "properties.wmqJms" stanza.
Thanks

推荐答案

Liberty 没有用于激活规范的等效参数/功能.您可以在此处提出改进请求:https://www.ibm/developerworks/rfe/?PROD_ID=544

Liberty doesn't have an equivalent parameter/capability for activation specs. You can open a request for enhancement here: https://www.ibm/developerworks/rfe/?PROD_ID=544

如果它在此期间有所帮助，模拟该功能的粗略方法是启动服务器并注释掉 jmsActivationSpec 元素，并在您希望激活它们时进行配置更新以取消注释.

In case it helps during the meantime, a crude way of simulating the capability is to start the server with the jmsActivationSpec elements commented out, and make configuration updates to uncomment as you want them activated.

这篇关于Liberty 上的 JMS 激活规范:“WAS_EndpointInitialState"完整配置文件等效属性?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！