Explore topic-wise InterviewSolutions in Current Affairs.

Spread Toolkit is a C++ library for messaging and only has partial support for JMS. It doesn't support DURABLE messaging, transactions, XA or full JMS 1.1. It is also dependent on a native code Spread daemon running on the machine.

Apache ActiveMQ on the other hand is the JMS provider used in Apache Geronimo and is J2EE 1.4 certified in Geronimo and is 100% pure JAVA. ActiveMQ supports transient and durable messaging, transactions, XA, J2EE 1.4, JMS 1.1, JCA 1.5 as WELL as heaps of different features like Message Groups and Clustering.

Spread Toolkit is a C++ library for messaging and only has partial support for JMS. It doesn't support durable messaging, transactions, XA or full JMS 1.1. It is also dependent on a native code Spread daemon running on the machine.

Apache ActiveMQ on the other hand is the JMS provider used in Apache Geronimo and is J2EE 1.4 certified in Geronimo and is 100% pure Java. ActiveMQ supports transient and durable messaging, transactions, XA, J2EE 1.4, JMS 1.1, JCA 1.5 as well as heaps of different features like Message Groups and Clustering.

You can monitor the STATUS of the connection with the broker via the addTransportListener() method on the ActiveMQConnection.

This method TAKES a TransportListener which is notified as the connection is established & dropped. It also allows you to work with the FAILOVER TRANSPORT yet STILL know the status of the connection.

You can monitor the status of the connection with the broker via the addTransportListener() method on the ActiveMQConnection.

This method takes a TransportListener which is notified as the connection is established & dropped. It also allows you to work with the Failover Transport yet still know the status of the connection.

OpenWire is the native protocol that APACHE ActiveMQ uses. It is DESIGNED for performance and size on the wire - sacrificing some ease of implementation with higher performance and reduced network bandwidth as a priority. OpenWire was first RELEASED in Apache ActiveMQ 4.0.

Stomp is a simpler text BASED protocol which is designed to be very simple to implement in a few hours in any language or PLATFORM (e.g. you can use a telnet client to communicate via Stomp). A Stomp client is not going to be as efficient as an client that uses
OpenWire, but it much simpler so you can generally be up and running with it much quicker.

OpenWire is the native protocol that Apache ActiveMQ uses. It is designed for performance and size on the wire - sacrificing some ease of implementation with higher performance and reduced network bandwidth as a priority. OpenWire was first released in Apache ActiveMQ 4.0.

Stomp is a simpler text based protocol which is designed to be very simple to implement in a few hours in any language or platform (e.g. you can use a telnet client to communicate via Stomp). A Stomp client is not going to be as efficient as an client that uses
OpenWire, but it much simpler so you can generally be up and running with it much quicker.

JMS compliance : ActiveMQ is an implementation of JMS ,so have all ADVANTAGES that JMS have.

Persistent : ActiveMQ has inbuilt KahaDB and it can be plugged to OUTSIDE DB as WELL.

Security : ActiveMQ provides authentication and AUTHORIZATION.

Cluster : Many ActiveMQ broker can make cluster to work together.

CLIENT API : ActiveMQ provides client API for many languages.

JMS compliance : ActiveMQ is an implementation of JMS ,so have all advantages that JMS have.

Persistent : ActiveMQ has inbuilt KahaDB and it can be plugged to outside DB as well.

Security : ActiveMQ provides authentication and authorization.

Cluster : Many ActiveMQ broker can make cluster to work together.

Client API : ActiveMQ provides client API for many languages.

Fuse MESSAGE Broker is a certified distribution of Apache ActiveMQ provided by FuseSource. FuseSource does all of its development and bug fixes as PART of the Apache ActiveMQ community, so there are no functional differences between the TWO. FuseSource may do more frequent releases than Apache, so it is possible to get bug fixes from a Fuse Message Broker release sooner than from an OFFICIAL Apache ActiveMQ release.

Fuse Message Broker is a certified distribution of Apache ActiveMQ provided by FuseSource. FuseSource does all of its development and bug fixes as part of the Apache ActiveMQ community, so there are no functional differences between the two. FuseSource may do more frequent releases than Apache, so it is possible to get bug fixes from a Fuse Message Broker release sooner than from an official Apache ActiveMQ release.

Artemis is the codename used for the HornetQ CODE that was donated to the Apache Foundation.

It is POSSIBLE that Artemis will eventually become the SUCCESSOR to ActiveMQ 5.x (and that it might eventually be branded as ActiveMQ 6.x), but no DECISION about that had been made as of APRIL 2015 as documented in that month's ActiveMQ Board Report.

Artemis is the codename used for the HornetQ code that was donated to the Apache Foundation.

It is possible that Artemis will eventually become the successor to ActiveMQ 5.x (and that it might eventually be branded as ActiveMQ 6.x), but no decision about that had been made as of April 2015 as documented in that month's ActiveMQ Board Report.

ActiveMQ 5.0-5.7 supports any JAVA platform of Java 5.0 or later. To run on 1.4 see these instructions. ActiveMQ 5.8-5.10 require Java 6 or higher and the releases from 5.11 ONWARDS require Java 7 or later.

ActiveMQ is based on J2EE 1.4 or later and so implements JMS 1.1 and a JCA 1.5 Resource Adaptor.

We regularly test ActiveMQ on Windows, OS X, Linux though we're aware of FOLKS who use AIX and Solaris too.

ActiveMQ 5.0-5.7 supports any Java platform of Java 5.0 or later. To run on 1.4 see these instructions. ActiveMQ 5.8-5.10 require Java 6 or higher and the releases from 5.11 onwards require Java 7 or later.

ActiveMQ is based on J2EE 1.4 or later and so implements JMS 1.1 and a JCA 1.5 Resource Adaptor.

We regularly test ActiveMQ on Windows, OS X, Linux though we're aware of folks who use AIX and Solaris too.

The test CASES in ActiveMQ can TAKE a very LONG TIME to run.

To disable this you can try the following
mvn install -Dmaven.test.skip=true

The test cases in ActiveMQ can take a very long time to run.

To disable this you can try the following
mvn install -Dmaven.test.skip=true

AMQP STANDS for the Advanced Message Queue Protocol and is a specification for how messaging clients and brokers can INTEROPERATE. AMQP is a specification of a wire-level protocol for client to message broker communication. It is not a messaging system like ActiveMQ, but just a messaging protocol.

ActiveMQ now implements AMQP 1.0

ActiveMQ also supports other open wire protocols:

• OpenWire, a fast binary format
• Stomp, a simple and easily implemented text based-protocol
• MQTT, a compact binary format for LIMITED DEVICES on an unreliable network

Through these protocols, ActiveMQ can support clients in C, C++, C#, Ruby, Python, Perl, PHP, Pike etc. AMQP is most similar to OpenWire, because both OpenWire and AMQP are designed for high performance messaging, through a binary (rather than text-based) format. As a text-based format, STOMP is much easier to implement, but gives SOMEWHAT slower performance.

AMQP stands for the Advanced Message Queue Protocol and is a specification for how messaging clients and brokers can interoperate. AMQP is a specification of a wire-level protocol for client to message broker communication. It is not a messaging system like ActiveMQ, but just a messaging protocol.

ActiveMQ now implements AMQP 1.0

ActiveMQ also supports other open wire protocols:

Through these protocols, ActiveMQ can support clients in C, C++, C#, Ruby, Python, Perl, PHP, Pike etc. AMQP is most similar to OpenWire, because both OpenWire and AMQP are designed for high performance messaging, through a binary (rather than text-based) format. As a text-based format, STOMP is much easier to implement, but gives somewhat slower performance.

• Activemq is used to reliably communicate between two distributed processes. It can store messages in a database to communicate between to 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 thousands of messages per second, databases TEND to fall over.
• Message ORIENTED middleware like ActiveMQ on the other hand are build to handle those use cases. They asume that messages in a healthy system will be deleted very quickly and can do optimizations to avoid the overhead. It can also push messages to consumers instead of a consumer having to poll for NEW message by doing a SQL query. This further reduces the latency involved in processing new messages being sent into the system.

Apache ActiveMQ is an open source message broker written in JAVA together with a full Java Message Service (JMS) client. It PROVIDES "Enterprise Features" which in this case MEANS fostering the communication from more than one client or server.

Apache ActiveMQ is an open source message broker written in Java together with a full Java Message Service (JMS) client. It provides "Enterprise Features" which in this case means fostering the communication from more than one client or server.