ActiveMQ Room for Improvement

Anonymous avatar x60
Senior Micro Service Developer via The Marlo Group (Contractor) at a financial services firm with 10,001+ employees
We have had problems with the message selector as when the queue size reaches a certain level, the message selector does not have enough time to run and finish before the JMS reply timeout. In this case the client will not consume the JMS reply message even when the correlation ID matches. Try not to use the feature but use the AMQ console which is much better. If you have to use , you may need to configure Jolokia, which is the JMX layer of, to display queues properly if you have a lot of queues. view full review »
1a91ff66 e4e2 44f2 89f8 4a85f2223dca avatar
Director of Data and Technology at a transportation company with 51-200 employees
I would like to see the following improvements: * The way it stores data * Needs to focus on a certain facet and be good at it, instead of handling support for most of the available message brokers. * For example, AMQP is a different flavor of message broker. However, adding it to ActiveMQ dramatically shifts its methodology and design. It can handle it, but it will be bad at it. Either you create a new forked solution of AMQ with AMQP and align only with AMQP, or just don't do it. view full review »
020abe0d c5d4 43fb a7b3 18b13d9b66d5 avatar
Principal Architect at a tech services company with 10,001+ employees
The master-slave relationship between brokers needs some improvement. In case of shared architecture between brokers (i.e., both brokers sharing same the DB instance), one becomes master and the others become slaves. In this situation, the master always consumes the message and the slave is always in a dormant condition. This makes load balancing impossible. Probably this can be improved upon. Another area of improvement is the monitoring console, which is kind of rudimentary. There is no facility to trace the entire XML message and take corrective action, such as resending the message. If these facilities are added, it will be very good. view full review »
50b993ba b8c7 4432 9980 bf85d46d65b4 avatar
Java Technical Lead at a tech services company with 5,001-10,000 employees
Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle. To clarify, it needs some queues in memory with the same abstract logic that ActiveMQ provides. An interesting example could be the embedded Redis framework, or the Derby database for integration tests. ActiveMQ does not persist the messages in the queue. So it would be fine if active has that feature, or some way to do it. So you can grab that message any time during the application lifecycle. Apache Kafka has that feature. The improvement could be the availability to persist the message in the queue for any time along the app running. Testing: I did not find a correct way to test the integration using Java, but rather only with manual testing. view full review »
Anonymous avatar x60
Senior System Administrator for Cloud Operations at a tech company with 1,001-5,000 employees
Apache ActiveMQ needs some improvement playing with multi-platform message clients. It already plays really well with Java clients since it’s a JMS implementation, but it needs some improvement supporting clients written in other languages (like C#). view full review »
Anonymous avatar x60
Project Staff at a financial services firm with 501-1,000 employees
There is need for more protocols and maybe they should provide documentation on the internet as well. During my summer internship, I developed a IoT application (a proof of concept). We had some Texas Instruments CC2650 sensors emitting to MQTT. For the first time, we wanted them to AMQP protocol with RabbitMQ, but the MQQT QoS 2 on RabbitMQ was a big problem. Thus, we switched to ActiveMQ. Unfortunately, we had to stay in MQTT, as ActiveMQ can’t translate protocols like RabbitMQ. In the end, we used the ActiveMQ broker to get the messages from our sensors (using the Java Library by Hiram Chirino, mqtt-client), then we parsed the messages from the sensors and stored them in Apache Hbase. With all of this data, we made some statistics, graphs and various other useful stuff for the industrials. About the documentation, it is more about the ActiveMQ advanced concepts such as using the KahaDB etc. For the protocols, maybe a translator is needed for example integration of AMQP to MQTT or XMPP to CoAP. view full review »
Anonymous avatar x60
Microservices Consultant at a transportation company with 501-1,000 employees
* Distributed message processing would be a nice addition. * An older version of ActiveMQ only provided failover, without a message spread across multiple nodes/broker. As with clusters (three nodes/broker), if one of the nodes goes down, other nodes should take the message and process it. If a message is consumed by a client, there was only one way to get the same message again. view full review »
Anonymous avatar x60
Consultant, Architect at a financial services firm with 201-500 employees
The included admin web app is not sufficient and we ended up disabling it. Instead, we are instead using hawtio and Jolokia. However, the audit logging in Jolokia is not detailed enough and we were forced to write our own audit filter. Even with hawtio, some JMX operations are awkward. A better admin tool would be nice. view full review »
09d5b64c 0687 4127 8149 847a69b7352a avatar
Senior Consultant at a tech vendor with 1-10 employees
Even though there is support from many open source communities, there is still weakness in ease-of-use and ease-of-configuration for more complex scenarios. The speed is not the highest ranking, but it's well known by users. They chose ActiveMQ for other features, because they know there are other messaging solutions that can work faster, like RabbitMQ, which is not Java written, but rather Erlang. view full review »
Anonymous avatar x60
Sr Software Engineer - Enterprise Automation Systems at a tech services company with 5,001-10,000 employees
The clustering for sure needs improvement. When we were using it, the only thing available was an active/passive relationship that had to be maintained via shared file storage. That model includes a single point of failure in that storage medium. view full review »
Anonymous avatar x60
Freelancer at a tech services company with 1,001-5,000 employees
I would like to see improvement in the clustering brokers. Configuring ActiveMQ brokers for working in a cluster is difficult and has many constraints. Also, the configuration files are not intuitive. view full review »
Anonymous avatar x60
Manager, Site Reliability Engineering at a energy/utilities company with 1,001-5,000 employees
It does not scale out well. It ends up being very complex if you have a lot of mirror queues. view full review »

Sign Up with Email