All the explanations so far are accurate and to the point – but might be missing something: one of the main benefits of message queueing: resilience. Imagine this: you need to communicate with two or three other systems. A common approach these days will be web services which is fine if you need an answers … Read more
RabbitMQ is an AMQP broker, while ActiveMQ is a JMS one. I suggest you read the AMQP wikipedia article to get an idea of the concepts used in AMQP, which are different than the ones you’re familiar in JMS. One of the main difference is that in AMQP a producer sends to an exchange without … Read more
There is a broker attribute, org.apache.activemq.broker.BrokerService#cacheTempDestinations that should help in the failover: case. Set that to true in xml configuration, and a temp destination will not be removed immediately when a client disconnects. A fast failover: reconnect will be able to producer and/or consume from the temp queue again. There is a timer task based … Read more
ActiveMQ is a message broker which implements the JMS API and supports a number of cross language clients and network protocols. It lets you implement queues or topics and write listeners or subscribers to respond to queue events. Mule and ServiceMix are open source ESB (enterprise service bus). An ESB has capabilities beyond JMS: queuing … Read more
Apache ActiveMQ is a great workhorse full of features and nice stuff. It’s not the fastest MQ software around but fast enough for most use cases. Among features are flexible clustring, fail-over, integrations with different application servers, security etc. Apache Apollo is an attempt to write a new core for ActiveMQ to cope with a … Read more
Kafka and ActiveMQ may have some overlaps but they were originally designed for different purposes. So comparing them is just like comparing an Apple and an Orange. Kafka Kafka is a distributed streaming platform with very good horizontal scaling capability. It allows applications to process and re-process streamed data on disk. Due to it’s high … Read more
It is used to reliably communicate between two distributed processes. Yes, you could store messages in a Database to communicate between two processes, but, as soon as the message is received you’d have to DELETE the message, That means a row INSERT and DELETE for each message. When you try to scale that up communicating … Read more
Apache received the code of HornetQ and they decided to change the name to Artemis and then the potential future ActiveMQ. But by looking to the latest news on their board, it seems the two projects are still distinct and ActiveMQ 5.15.x is still using the old ActiveMQ core source code. Apparently they need to … Read more
That means a topic is appropriate. A queue means a message goes to one and only one possible subscriber. A topic goes to each and every subscriber.
I used the following two steps which I found in the comments/posts linked in the other answers: Step one: Convert the x.509 cert and key to a pkcs12 file openssl pkcs12 -export -in server.crt -inkey server.key \ -out server.p12 -name [some-alias] \ -CAfile ca.crt -caname root Note: Make sure you put a password on the … Read more