AMQP Amqp绑定IIS / WAS问题？ [英] AMQP AmqpBinding IIS/WAS problems?

问题描述

当前雇主的设置在Java平台上有一组后台功能，在两个独立的基于.NET的平台上有另一组功能。没有整体架构师。

The setup at the current employer has one set of back office functions on a Java platform and another group of functions on two separate .NET-based platforms. There is no overall architect.

Java家伙决定使用.NET QPID和AMQP进行消息传递，可能是他们自己的.NET系统和其他外部系统。

The Java guys decided to go for Apache QPID and AMQP for messaging, presumably amongst themselves, with the .NET systems and other external systems.

.NET体系结构涉及IIS / WAS和Windows Server AppFabric中托管的WCF服务。

.NET architecture involves WCF services hosted in IIS/WAS and Windows Server AppFabric.

如果有任何可能的陷阱，有没有人有AmqpBinding和IIS / WAS的经验？

Does anyone have any experience of AmqpBinding and IIS/WAS, if there are any possible pitfalls?

推荐答案

我认为你的第一个问题是IIS / WAS / AppFabric，因为WAS中托管的非HTTP服务对基础设施有额外的要求，这些要求包括通常像windows服务一样运行的额外进程（监听器）和通信与工人进程。此过程负责接收和发送消息，并允许在WAS中激活服务。我不认为QPID项目已经创建了监听器进程。您很可能必须自己实现监听器 - 请查看此示例自定义UDP激活器。

I think your first problem will be IIS/WAS/AppFabric because non HTTP services hosted in WAS have additional requirements for infrastructure which consists of additional process (listener) running usually as as a windows service and communicating with worker process. This process is responsible for receiving and sending messages and allows service activation in WAS. I don't think that the QPID project has the listener process already created. You will most probably have to implement the listener yourselves - check this sample for custom UDP activator.

这篇关于AMQP Amqp绑定IIS / WAS问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！