简体繁体 English

关于使用TIBCO .Net客户端进行JMS集成的最佳实践

[英]About best practices of JMS integration using TIBCO .Net client

原文 2010-01-30 14:57:05 4 1 .net/ integration/ tibco

I'm working on an integration project where I'm talking to JMS framework using TIBCO .Net client. 我正在一个集成项目中，正在使用TIBCO .Net客户端与JMS框架进行对话。 A colleague is recommdending a design decision based on a fear of receiving too many messages suddenly in a way that our application can't handle it. 一位同事基于担心突然收到太多消息而以我们的应用程序无法处理的方式来推荐设计决策。 We are using Asynchronous mode while receiving messages. 我们在接收消息时正在使用异步模式。 I'm new to that topic so I couldn't find quick best practices to support his clam or mine. 我是该主题的新手，所以找不到支持他的蛤c或我的蛤的快速最佳实践。 Any suggestions? 有什么建议么？ How can I test this subject? 我该如何测试这个学科？

1 个解决方案

After I tested the subject for a while I found out there's no fear of number of received messages. 经过一段时间的测试，我发现不必担心收到的邮件数量。 The major point won't be in receiving itself but in the processing of received message. 重点不是接收自身，而是处理接收到的消息。 This is what determines the actual performance of application. 这决定了应用程序的实际性能。

In a previous design, We have separated the Receiver component from Processor component & That resulted in delay because we have to wait till receiver finishes then to start processing received messages via the another component. 在以前的设计中，我们将接收器组件与处理器组件分开了，这导致了延迟，因为我们必须等到接收器完成后才能开始通过另一个组件处理接收到的消息。

This design is being changed now. 现在正在更改此设计。 So, processing should be immediately upon a message reception. 因此，应该在收到消息后立即进行处理。 Message receiving should be Asynchronously through handling the event MessageHandler of type EMSMessageHandler and this is the best practice for message receiving so far. 通过处理类型为EMSMessageHandler的事件MessageHandler，消息接收应该是异步的，这是到目前为止消息接收的最佳实践。