Written in Java - HornetQ runs on any platform with a Java 5 or later runtime.

JMS and above - HornetQ supports the JMS 1.1 and 2.0 APIs and also defines its own messaging API for maximum performance and flexibility. Other protocols are planned for upcoming releases.

Superb performance - HornetQ class-beating high performance journal provides persistent messaging performance at rates normally seen for non-persistent messaging. Non-persistent messaging performance rocks the boat too.

POJO-based design - HornetQ has been designed using POJO and minimal third-party dependencies. You choose how you want to use HornetQ: run it stand-alone, integrate it with JBoss Application Server or another Java server/container or embed it directly inside your own product.

Solid high availability - HornetQ offers server replication and automatic client failover to eliminate lost or duplicated messages in case of server failure.

Flexible clustering - Create clusters of HornetQ servers that know how to load balance messages. Link geographically distributed clusters over unreliable connections to form a global network. Configure routing of messages in a highly flexible way. Adapt HornetQ to your network topology, not the other way round.

Management - HornetQ provides a comprehensive management API to manage & monitor servers. It is integrated seamlessly to the servers to work in a highly available environment.

Programming language: - - -
License: Apache License 2.0
Tags: Queuing     Clustering     Queue     JBoss     JMS     POJO    

HornetQ alternatives and similar tools

Based on the "Queuing" category.
Alternatively, view JBoss HornetQ alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of HornetQ or a related project?

Add another 'Queuing' Tool



If you need information about the HornetQ project please go to



This file describes some minimum 'stuff one needs to know' to get started coding in this project.


The project's source code is hosted at:


Git usage:

Pull requests should be merged without fast forwards '--no-ff'. An easy way to achieve that is to use

% git config branch.master.mergeoptions --no-ff


HornetQ is now in maintenance mode. the master / upstream for hornetq is now ActiveMQ Artemis

  • 2.3.x is the branch used for EAP.
  • 2.4.x was the branch used on Wildfly up until recently, Wildfly also moved to Artemis on newer releases
  • master has been discontinued