((I accidentally deleted a bunch of comments I didn’t mean to delete today, so I’m having to repost them manually:))

Pedro Melo wrote:

Hi,

great work!

Now that ejabberd supports (version 2.x and up) pluggable back.-end’s to their pubsub stuff, are there any plans to make mod_rabbitmq such a module?

this would allow us to use XEP-0060 (PubSub over XMPP) with RabbitMQ topics.

Thanks,

((I accidentally deleted a bunch of comments I didn’t mean to delete today, so I’m having to repost them manually:))

Mickaël Rémond wrote:

Hello,

This sounds like a good idea.
If you want to, we would be happy to give you an access to ejabberd-modules svn for your ejabberd module gateway code.

We try to gather as much as possible of the modules developed for ejabberd in this space.

http://svn.process-one.net/ejabberd-modules/

Let me know

–
Mickaël Rémond
http://www.process-one.net/

@Pedro: That’s an interesting idea. I haven’t yet had a look to see how difficult it might be, but if pubsub and AMQP can be fit together reasonably smoothly, it would definitely be a good idea to do so.

@Mickael: Thanks very much. It’s still pretty experimental, and will probably evolve fairly rapidly. Once it settles down a little, we’d be happy to contribute it to the ejabberd community.

The repository seems to be down.

Thanks for the heads-up, Bryan — we’re looking into the problem.

Oops, I broke that while working on something else. Sorry! Fixed now. Bryan - thanks for letting us know.

Hi. I am having trouble compiling the RabbitMQ XMPP gateway into ejabberd. I am working from the Mercurial trunk for the gateway code (27:944d554c2827), and the ejabberd trunk (r1823) and RabbitMQ trunk (772:75288d1eae96). Erlang is R12B5 on Ubuntu Intrepid.

Here are the errors I am seeing after I linked the gateway code into the ejabberd src dir and try to re-compile ejabberd:

And here is the full output as well as the tiny script I am using to help me compile:

http://gist.github.com/48765

Can anyone offer any insights? I am not well versed in Erlang so diagnosing the issue is tough for me.

Thanks!

Hi Glenn — thanks for posting. The mailing-list thread starting here http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2009-January/003030.html discusses the current problems we’re having getting the XMPP gateway to work. In brief, there’s a mnesia table name clash between RabbitMQ and ejabberd, and we will need to add a unique prefix (e.g. “rabbitmq_”) to all our table names.

Just to clarify, the XMPP gateway is known to work with RabbitMQ 1.4.x; it will not work with 1.5.x (because of the mnesia table name clash); and it will most likely be fixed again sometime before the release of 1.6.0.

Hi tonyg, does the gateway work with the current RabbitMQ 1.7.x?

@jiannis: It should! However, since it’s not an official Rabbit release, you are probably better off taking the “default” branches of both rabbitmq and the xmpp gateway from mercurial, and building them yourself.

To clarify, the problem I mentioned above that affected RabbitMQ 1.5.x with the XMPP gateway has been fixed long ago.

Hi Tony and thanks for the quick response!

Using RabbitMQ server 1.7.2 after having compiled the gateway code (73c129561101) against ejabberd 2.1.3 and configured as described in the overview document with everything running in localhost. When starting ejabberd though and increasing the log level to debug, modrabbitmq throws an exception in function “exception exit: {{badmatch,{contactingrabbitmq,rabbit@mixer,pang}} in genserver:initit/6″ - rabbit@mixer is the local host.

Can you offer any insights? Is it a configuration issue or I should be looking elsewhere? I am not familiar with Erlang so tracking down the issue by going through the code is a bit difficult for me. Any pointers on where to look? Looking forward to getting this baby going.. :)

It’s probably an erlang clustering problem. Try either making your ejabberd VM “ejabberd@mixer”, or making your rabbit VM “rabbit@localhost”.

Great, thanks tony!

It was indeed a configuration issue having to do with the way Mac OS X resolves local hosts - rabbit@machine.local instead of rabbit@machine!

For anyone trying the same you might want to check out the “-name” and “-sname” arguments of the erlang process that starts the ejabberd and RabbitMQ servers as well as Apple support article HT2385 and make sure that the erlang cookies are the same.

What actually helped in tracking this down was first getting two erl shells to ping each other!

Thanks again, lots of love for this product, works great!

Where can I find a copy of mod_rabbitmq? I can’t seem to find it anywhere, the rabbitmq-xmpp repo seems to have disappeared, all the links to it from above don’t work anymore.