带有 WLS 外部服务器的 MQ
当我尝试通过创建外部服务器连接到从 Weblogic Server(WLS) 部署在远程服务器上的 MQ 时，我遇到两个问题。 1. 当我尝试以绑定模式连接到 MQ Queuemanager 时（导入 .Bindings 文件后），我在 WLS 控制台中不断收到以下错误：
java.lang.UnsatisfiedLinkError：java.library.path中没有mqjbnd05
- 如果我将传输切换到客户端，我不断收到：
JMSWMQ0018：无法使用连接模式“客户端”和主机名“localhost”连接到队列管理器“”。检查队列管理器是否已启动，如果在客户端模式下运行，请检查是否有侦听器正在运行。请参阅链接的异常以获取更多信息。
有没有人看到过这一点，是否有任何性能影响决定使用客户端而不是绑定，反之亦然？
TIA
I am facing two issues when i try to connect to MQ which is deployed on a Remote Server from Weblogic Server(WLS) by creating a Foreign Server.
1. When I try to connect to MQ Queuemanager in Bindings mode(after importing the .Bindings file) i keep getting the below error in WLS console:
java.lang.UnsatisfiedLinkError: no mqjbnd05 in java.library.path
- If i Switch the Transport to Client i keep getting:
JMSWMQ0018: Failed to connect to queue manager '' with connection mode 'Client' and host name 'localhost'. Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information.
Has anyone seen this, and are there any performance implications which dictate the use of client over bindings and vice versa?
TIA
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
最后我能够解决这个问题，我必须在客户端模式下重新创建 .bindings 文件，并对 IVTsetup.bat 进行更改，该文件很可能存在于
C:\Program Files\IBM\WebSphere MQ\java\bin，我必须运行这个
def qcf(psQCF) 传输（客户端） 主机（SMEKA） 端口（1415） 通道（ps_SRV_CHANNEL） QMGR（psQM）
生成 .bindings 文件。
请参阅此链接了解更多详细信息：
Finally i was able to resolve this, i had to recreate the .bindings file in the client mode, with changes to the IVTsetup.bat which is most likely present in
C:\Program Files\IBM\WebSphere MQ\java\bin, I had to run this
def qcf(psQCF) TRANSPORT(CLIENT) HOST(SMEKA) PORT(1415) CHANNEL(ps_SRV_CHANNEL) QMGR(psQM)
to generate the .bindings file.
Refer to this link for more details:
如果问题指出我尝试从 Weblogic Server 连接到部署在远程服务器上的 MQ，我认为这意味着 WLS 和 WMQ 位于两个不同的主机上。如果是这种情况，则绑定模式连接（依赖于共享内存段）将不起作用。
客户端模式连接似乎使用指向 localhost 而不是 WMQ 服务器的 IP 或主机名的 CF。这适用于与队列管理器位于同一主机上的应用程序，但当应用程序和 QMgr 位于不同的服务器上时则无效。
至于在客户端和绑定模式之间进行选择，答案是如果 QMgr 是本地使用绑定。这提供了最高的可靠性、最佳的性能和 XA 事务性。使用客户端模式时，如果没有扩展事务客户端，则不支持两阶段 XA 提交。根据 JMS 规范，如果应用程序在 COMMIT 调用期间丢失连接，则可能存在歧义。根据应用程序处理此问题的方式，最终可能会出现重复的消息。 （JMS 规范将这些称为“功能上重复”。）这种歧义在绑定模式连接中不太可能发生，因为没有网络延迟，甚至没有任何 IP 堆栈或的遍历。界面。因此，尽可能使用绑定模式。
更新：
删除了有关扩展事务客户端是收费组件的注释。 自 4 月 24 日起，XTC 对所有平台上的所有 WMQ 版本都是免费的。
Where the question states that I try to connect to MQ which is deployed on a Remote Server from Weblogic Server I assume this means that WLS and WMQ are on two different hosts. If that is the case, then a bindings mode connection (which relies on shared memory segments) won't work.
The client mode connection appears to be using a CF that is pointed to localhost rather than the IP or hostname of the WMQ server. This would work for an application on the same host as the queue manager but not when the app and QMgr are on separate servers.
As far as choosing between client and bindings mode, the answer is that if the QMgr is local use bindings. This provides highest reliability, best performance and XA transactionality. When using client mode, two-phase XA commit is not supported without the Extended Transactional Client. Per the JMS specification, there is an ambiguity that can exist if an app loses the connection during a COMMIT call. Depending on how the app handles this it's possible to end up with duplicate messages. (The JMS spec refers to these as "functionally duplicate.") This ambiguity is much less likely to occur with a bindings mode connection since there is no network latency and not even any traversal of the IP stack or interface. So use bindings mode where possible.
UPDATE:
Removed note about Extended Transactional Client being a chargeable component. As of April 24th, XTC is free of charge for all versions of WMQ on all platforms.