CODEWITHSUNDEEP
.netwcfrabbitmqamqpwas
mthornal
mthornal

Reputation: 395

RabbitMQ WCF service hosting in IIS/WAS

I would like to use RabbitMQ (as a replacement for MSMQ) with WCF and I'd like to host these WCF services in IIS/WAS. Unfortunately it seems from the documentation that accompanies the RabbitMQ .NET client library that this configuration is "untested and unsupported".

I'm no WCF expert, but my understanding is that the reason for this being unsupported is because the RabbitMQ WCF implementation uses a completely new transport binding element. WAS has no knowledge of this and based on my reading of this article: http://msdn.microsoft.com/en-us/magazine/cc163357.aspx would require some unmanaged software writing in order for WAS to properly setup the routing of incoming AMQP messages to the appropriate IIS application and service endpoint.

I'd be grateful if anyone could confirm whether my understanding is correct and/or whether there are any alternative approaches to hosting a RabbitMQ WCF service in IIS/WAS without needing to write any unmanaged code e.g. perhaps a customisation of the net.tcp transport binding element?

Upvotes: 2

Views: 3761

Answers (1)

Sentinel
Sentinel

Reputation: 3697

See this question: AMQP AmqpBinding IIS/WAS problems?

A response there points to the UDP Activator sample. I have a similar problem. I would like to use IIS/WAS for all the benefits that AppFabric brings, and I want to allow push messaging over the MQ.

If I find any other options apart from writing a new AMQP activator listener I will try to document them here. Can't believe that WAS isn't ready for this.

Upvotes: 1

Related Questions