Live data from Hacker News

ActiveMQ: Not ready for prime time

goodstuff.im

11–20 of 93 posts

Re: ActiveMQ: Not ready for prime time

#12
post #10

> It's not correctly configured out of the box. You mean there's a correct configuration? Also, Tomcat, Jetty, PostgreSQL, and Ngnix don't "install correctly" out of the box as described here. Tomcat clusters set themselves up? Postgres? Hell, I think default shared buffers allocation is 32 MB... > Anything that streams bytes I'm not sure what the author is trying to do. Doesn't sound like queuing to me... The docume…

Well, if every piece of enterprise software worked right out of the box, consultants would be out of business.

I have to admit that I'm not a big user of ActiveMQ, but I've used a closed-source equivalent from a slightly bigger vendor (IBM) for many years. It also is not configured correctly out of the box for most enterprises. When new features or platforms come out they are often buggy. The documentation though is usually decent until you really want to dig into the internals and understand it.

Re: ActiveMQ: Not ready for prime time

#14
I used ActiveMQ in a large production environment for two years. It's by a large margin the worst piece of software I've used professionally. You wouldn't believe the number of very serious problems we had with it (including some mentioned here, like negative queue lengths, but mostly broker crashes, missing or wrong documentation, outright broken features, serious threading issues, and poor performance). If anyone's not convinced, just peek at the source code. It's frightening.

We ended up writing a new queuing system from scratch in a month, and in its first week it was already more stable, performant, and bug-free than ActiveMQ.

Re: ActiveMQ: Not ready for prime time

#15

Does anyone have recommendations for resources on messaging/queueing basics? I'm look for something on the basic patterns (pubsub, broadcast... ?) and basic considerations to be aware of.

As far as considerations to be aware of, Second Life posted their message queue evaluation notes: http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Not...

Re: ActiveMQ: Not ready for prime time

#16

I used ActiveMQ in a large production environment for two years. It's by a large margin the worst piece of software I've used professionally. You wouldn't believe the number of very serious problems we had with it (including some mentioned here, like negative queue lengths, but mostly broker crashes, missing or wrong documentation, outright broken features, serious threading issues, and poor performance). If anyone's…

Hi - this is pretty damning. We're currently building an application that uses ActiveMQ but I could switch to a different broker if I thought it was justified. Do you remember which version you were using?

Re: ActiveMQ: Not ready for prime time

#18
post #10

> It's not correctly configured out of the box. You mean there's a correct configuration? Also, Tomcat, Jetty, PostgreSQL, and Ngnix don't "install correctly" out of the box as described here. Tomcat clusters set themselves up? Postgres? Hell, I think default shared buffers allocation is 32 MB... > Anything that streams bytes I'm not sure what the author is trying to do. Doesn't sound like queuing to me... The docume…

Yes, streaming doesn't sound like queueing, but both JMS (and many vendors implement JMS) and AMQP support some form of streaming. Of course, in combination with high availability, YMMV.

Re: ActiveMQ: Not ready for prime time

#19
post #10

> It's not correctly configured out of the box. You mean there's a correct configuration? Also, Tomcat, Jetty, PostgreSQL, and Ngnix don't "install correctly" out of the box as described here. Tomcat clusters set themselves up? Postgres? Hell, I think default shared buffers allocation is 32 MB... > Anything that streams bytes I'm not sure what the author is trying to do. Doesn't sound like queuing to me... The docume…

The part about Tomcat certainly isn't true, unless the author is using a different distribution than what you get from the project's website. The Tomcat startup scripts do not set any heap size paramters; until recently the default Sun JVM behavior was to set a max heap size of only 64MB. This logic changed a few versions ago to use a fractional amount of the total memory size on the machine, but for dedicated hosts this is still rarely the setup you want.

Perhaps the author is using a packaged version of Tomcat from his OS distributor.

Re: ActiveMQ: Not ready for prime time

#20

I used ActiveMQ in a large production environment for two years. It's by a large margin the worst piece of software I've used professionally. You wouldn't believe the number of very serious problems we had with it (including some mentioned here, like negative queue lengths, but mostly broker crashes, missing or wrong documentation, outright broken features, serious threading issues, and poor performance). If anyone's…

Hi - this is pretty damning. We're currently building an application that uses ActiveMQ but I could switch to a different broker if I thought it was justified. Do you remember which version you were using?

I believe it was 5.0 and 5.1.
Post reply on HN