MSMQ，WCF和Flaky服务器 [英] MSMQ, WCF, and Flaky Servers

问题描述

我有两个应用程序，我们称它们为A和B.当前A使用WCF向B发送消息.A不需要响应，B从未将消息发送回A.

I have two applications, let us call them A and B. Currently A uses WCF to send messages to B. A doesn't need a response and B never sends messages back to A.

不幸的是，正在运行的服务器A和B之间存在不稳定的网络连接.这会导致A有时会出现超时错误.

Unfortunately, there is a flaky network connection between the servers A and B are running on. This results in A getting timeout errors from time to time.

我想使用WCF + MSMQ作为两个应用程序之间的缓冲区.这样，如果B暂时掉线或无法访问，则消息不会丢失.

I would like to use WCF+MSMQ as a buffer between the two applications. That way if B goes down temporarily, or is otherwise inaccessible, the messages are not lost.

从体系结构的角度来看，我应该如何配置?

From an architectural standpoint, how should I configure this?

推荐答案

我认为您可能会因为包含建筑"一词而使问题有点夸张.

I think you might have inflated your question a bit with the inclusion of the word "architectural".

如果您确实真正需要从更高层次上对此问题进行体系结构概述，包括对SLA的关注，则您的SL将与您的MSMQ部署一样好，因此，如果您担心SL，只需查看Internet上有关MSMQ和SLA的文档即可.

If you truly need an architectural overview of this issue from that high of a level, including SLA concerns, your SL will be as good as your MSMQ deployment, so if you are concerned about SL, just look at the documentation on the internet about MSMQ and SLA.

如果您希望从代码的角度进一步寻找实际的实现方式，那么本文非常出色: http://code.msdn.microsoft.com/msmqpluswcf

If you are looking more for the actual implementation from a code standpoint, this article is excellent: http://code.msdn.microsoft.com/msmqpluswcf

它涉及了许多您需要了解的事情，包括如何设置MSMQ以及如何实现分块以克服MSMQ的4MB限制(如果有必要，我希望不是).

It goes over a lot of the things you'll need to know, including how to setup MSMQ and how to implement chunking to get around MSMQ's 4MB limit (if this is necessary... I hope it's not).

这是一篇有关创建持久性事务性队列的优秀文章，该队列将使用MSMQ群集跨计算机:

Here's a good article about creating a durable and transactional queue that will cross machines using an MSMQ cluster: http://www.devx.com/enterprise/Article/39015/1954

这篇关于MSMQ，WCF和Flaky服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！