<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">For what it's worth I've been using RabbitMQ in a production system running 24/7 for more than 2 year, running flawlessly. I wouldn't hesitate to use it again.<div><br></div><div>Whether it will solve your specific issues or not, I can't tell.</div><div><br></div><div>Also, I believe in the AMQP standard effort as I feel less "locked in" than with other solutions.</div><div><br></div><div>YMMV.</div><div><br></div><div>Regards,</div><div><br></div><div>Michael Arnoldus</div><div><br><div><div>On Aug 29, 2009, at 16:20 , Dikkie Hagel wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="hmmessage" style="font-size: 10pt; font-family: Verdana; ">Hello,<br><br>I am in the process of setting up messaging middleware for a webbased platform which should be able to handle millions producers/consumers.<br><br>We've started our development with ActiveMQ. Everything seemed to work fine until we started connecting with 1000 consumers to a single topic. ActiveMQ could not handle this at all, complaining about "too many open filehandles". Others seem to have encountered this same issue as well (see second life's review), but we've not been able to google a solution. That was a major showstopper, and made us conclude that something was terribly wrong with the architecture of this software, which made it unsuitable for our intended purpose.<br><br>We then turned to RabbitMQ, and after fixing the Perl and ActionScript AMQP interfaces (<a href="http://github.com/joodie">http://github.com/joodie</a>) we now almost have a working prototype for our environment, ready for some first performance tests.<br><br>Now I just received a mail from the ActiveMQ/Fuse support team, which in reply to my report to them about the 1000 consumers issue, quotes their "Manager Engineering", stating the following:<br><br>============== START OF QUOTE =================<br>This is due to the configuration out of the box for ActiveMQ - its very<br>straightforward for ActiveMQ to handle the same load as RabbitMQ.<br>There are some significant benefits in using ActiveMQ over RabbitMQ.<br>ActiveMQ has no limit on the depth (number of messages) in a Queue -<br>other than disk space. RabbitMQ runs out of memory.<br>Also - there's performance benefits too - although sending messages can<br>be a lot faster to RabbitMQ (this is due to RabbitMQ caching messages in<br>memory) - consuming messages is considerably slower.<br>In reality, RabbitMQ is just hype ware - not really suitable for<br>production scenarios. Although its getting a lot of traction, it only<br>suitable for cases where consumers will always keep up with producers.<br>=============== END OF QUOTE ======================<br><br>Now that's a pretty scary assesment there. "Hype ware"... Perhaps RabbitMQ's engineers can reply to this, and reassure us that our shift in favour of RabbitMQ is a sound decision? (we plan to deploy it on systems with plenty gigs of RAM).<br><br>Kind regards, Roberto<br><hr>What can you do with the new Windows Live?<span class="Apple-converted-space"> </span><a href="http://www.microsoft.com/windows/windowslive/default.aspx" target="_new">Find out</a>_______________________________________________<br>rabbitmq-discuss mailing list<br><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br><a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br></div></span></blockquote></div><br></div></body></html>