ActiveMQ: Not ready for prime time • Hacker News Board

Re: ActiveMQ: Not ready for prime time

#91

Post by tvaillancourt » Fri, May 27, 2011, 7:34 PM UTC

We use ActiveMQ in production. I couldn't agree more that it is not ready for prime time. We've had a pretty bad experience overall. Man I wish we used Amazon SQS...

We have had incidents where it's Master/Slave replication continues on failure when configured to shutdown the master and slave brokers. It doesn't achieve the consistency it lists as a feature, and provides zero visibility of progress. I feel many of the features the project lists are incomplete, and are listed as a grasp at straws to have the bigger list.

Due to the poor quality of the replication, we had to invest a tonne of time to implement replication at the block device level with DRBD+GFS2, complicating the system and (benchmarks pending) likely decreasing performance, all to achieve a 'feature' ActiveMQ boasts.

I would also challenge a project to have worse, more incomplete documentation.

At the same time, I thank the ActiveMQ team for their contributions and ask the community to not turn it's back on this potentially decent solution. The ideas are solid. It isn't production ready, I feel, but that just means it needs some love.

Cheers,

Tim Vaillancourt

Re: ActiveMQ: Not ready for prime time

#92

Post by wslh » Sat, May 28, 2011, 4:24 PM UTC

rabbitmq wrote: post #80

wslh wrote: post #61

There is a lot of buzz about open source queue systems. I have tried for example the RabbitMQ with very bad results. I'll rather explain... one interesting concept about queues is contention and this is where RabbitMQ and others are behind. The strange thing is that contention is an old concept from the old mainframes. For example the last time I checked you can't block a produced in RabbitMQ based on the number of m…

If you have any questions or problems involving RabbitMQ please email us (info@rabbitmq.com) or post to the mailing list. "one interesting concept about queues is contention and this is where RabbitMQ and others are behind" Can you explain what this means? What kind of contention are you talking about. You say "RabbitMQ and others" - which others? Who implements this feature and what does it look like? "you can't blo…

Please let me know where I am wrong:

- RabbitMQ has a memory based flow control based on the total memory you have in the machine. I know I can develop something over RabbitMQ to accomplish what I want (limits based on number of messages) but I prefer to have the support within RabbitMQ.

- WebLogic JMS can block producers based on number of messages as a flow control method.

Re: ActiveMQ: Not ready for prime time

#93

Post by rabbitmq » Sat, May 28, 2011, 7:36 PM UTC

wslh wrote: post #92

rabbitmq wrote: post #80

Earlier quoted context omitted.

If you have any questions or problems involving RabbitMQ please email us (info@rabbitmq.com) or post to the mailing list. "one interesting concept about queues is contention and this is where RabbitMQ and others are behind" Can you explain what this means? What kind of contention are you talking about. You say "RabbitMQ and others" - which others? Who implements this feature and what does it look like? "you can't blo…

Please let me know where I am wrong: - RabbitMQ has a memory based flow control based on the total memory you have in the machine. I know I can develop something over RabbitMQ to accomplish what I want (limits based on number of messages) but I prefer to have the support within RabbitMQ. - WebLogic JMS can block producers based on number of messages as a flow control method.

I don't know what WebLogic can do for flow control exactly. Please email rabbitmq-discuss to get a definitive answer and discussion on what you can do with Rabbit, which supports various mechanisms.