如何监视来自TIBCO EMS .Net客户端的传出消息? [英] How to monitor outgoing messages from TIBCO EMS .Net client?

问题描述

使用.Net客户端TIBCO EMS时，如何监视来自.Net Tibco客户端的传出消息?

While using the .Net client TIBCO EMS, How to monitor outgoing messages from my .Net Tibco client?

我将发送应用程序级别(而不是jms级别)的确认和答复. 我怎么知道应用程序是否发送了?如果客户端无法发送消息，它将抛出异常或存储消息以供稍后重试?

I'm going to send Application-level, not jms-level, acknowlegements and replies. How can I tell If the application sent them or not? If the client failed to send a message will it throw an exception or store the message to try again later?

最重要的是，有没有什么工具可以使我从客户的角度监视活动(发送)?

Bottom line, Is there any tool enables me to monitor activities(outgoing) from client point of view?

推荐答案

使用.Net客户端TIBCO EMS时， 如何监视来自的外发消息 我的.Net Tibco客户?

While using the .Net client TIBCO EMS, How to monitor outgoing messages from my .Net Tibco client?

您要监视的确切是什么，是总线/EMS上的实际消息还是客户端(不包括客户端库)的工作情况?我会在下面回答的第一个，第二个可以通过常规日志记录来处理.我建议为此使用log4Net或类似的库.

What is it exactly that you want to monitor, is it the actual messages on the bus/EMS or the workings of your client (not including the client libraries)? The first I'll answer below, the second you can handle with regular logging. I suggest log4Net or similar library for that.

我将发送应用程序级别， 不是jms级，致谢和 回覆.我怎么知道 申请是否发送给他们?

I'm going to send Application-level, not jms-level, acknowlegements and replies. How can I tell If the application sent them or not?

我建议您在内部在客户端dll级别之上记录此日志(请参阅下一个问题).

I suggest you log this internally just above the client dll level (see next question).

如果客户端发送消息失败 它会抛出异常还是存储 消息以供稍后重试?

If the client failed to send a message will it throw an exception or store the message to try again later?

根据特定问题，EMS客户端dll将抛出异常，或者在连接丢失的情况下尝试重新连接.在第二种情况下，尝试次数取决于连接工厂的配置方式(请咨询EMS管理员).

Depending on the specific problem the EMS client dlls will either throw an exception or in the case of a lost connection, attempt to reconnect. In the second case the number of attempts depends on how the connection factory is configured (ask your EMS administrator).

客户端抛出的异常取决于问题，它们都继承自TIBCO.EMS.EMSException，并且都在您的API文档中列出(！).

The exceptions thrown by the client depend on the problem, they all inherit from TIBCO.EMS.EMSException and they are all listed in your API documentation(!).

底线，是否有任何启用工具 我监视活动(去向) 从客户的角度来看?

Bottom line, Is there any tool enables me to monitor activities(outgoing) from client point of view?

有几种工具可让您监视EMS和特定的目的地.在监视目的地时，他们很可能会使用Anders和c提到的监视主题.廖(一个实际的示例是"$ sys.monitor.Q.*.queue.sample").订阅监视主题就像订阅任何其他主题一样，并且可以通过客户端库进行订阅，因此您不需要特定的工具.但是，您确实需要提升的用户权限.

There are several tools that will allow you to monitor the EMS and specific destinations. When monitoring destinations they will most likely use the monitoring topics mentioned by both Anders and c. liau. (a practical example is "$sys.monitor.Q.*.queue.sample"). Subscribing to a monitor topic is like subscribing to any other topic and is possible with the client libraries, you do not need a specific tool for this. You do however need elevated user rights.

在我看来，您的客户端库没有足够的文档.我个人认为不需要从您的应用程序监视目的地，实际上，我会强烈质疑该设计.正确的异常处理和内部日志记录应该足以解决当前的问题.

It sounds to me like you have not gotten sufficient documentation with your client libraries. Personally I do not see the need for monitoring your destinations from your application, in fact I would strongly question that design. Correct exception handling and internal logging should be sufficient to solve the problem at hand.

这篇关于如何监视来自TIBCO EMS .Net客户端的传出消息?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！