Skip to main content

Eclipse OpenMQ

Eclipse OpenMQ is an open-source message broker and client implementation for the Java Message Service (JMS) (messaging middleware), providing standards-based messaging infrastructure for Java and Jakarta EE applications.

  • Implements the Java Message Service (JMS) specification for reliable, asynchronous messaging (messaging middleware).
  • Provides a message broker and client libraries for Java and Jakarta EE environments (application integration).
  • Supports point-to-point and publish/subscribe messaging models defined by JMS (messaging patterns).
  • Integrates with Jakarta Messaging in the Eclipse EE4J ecosystem (Jakarta EE platform integration).
  • Distributed under the Eclipse Foundation governance and open-source licensing model (open-source governance).

More About Eclipse OpenMQ

Eclipse OpenMQ is a message-oriented middleware (messaging infrastructure) that implements the Java Message Service (JMS) specification and serves as the reference implementation in the Jakarta Messaging and Eclipse EE4J ecosystem. It provides a standards-based way for Java and Jakarta EE applications to exchange messages asynchronously, decoupling producers and consumers and enabling reliable communication across distributed systems.

The project delivers a message broker (message server) and corresponding client libraries (messaging middleware) that support the core JMS programming model. This includes point-to-point queues and publish/subscribe topics, durable and non-durable subscriptions, and standard JMS message types. Because it adheres to the JMS and Jakarta Messaging specifications (enterprise messaging standards), OpenMQ can be used wherever those APIs are supported, including within Jakarta EE application servers and standalone Java applications.

In enterprise environments, Eclipse OpenMQ is used as a messaging backbone (enterprise integration) to connect business services, back-end systems, and integration components using a common Application Programming Interface (API). Applications can send and receive messages without direct knowledge of each other, which supports loose coupling, reliability, and asynchronous workflows. OpenMQ can be deployed as a standalone broker process or integrated as part of a Jakarta EE runtime that uses Jakarta Messaging to route messages between enterprise components such as message-driven beans.

OpenMQ is developed under the Eclipse EE4J umbrella (Jakarta EE ecosystem), which aligns it with the broader Jakarta EE platform and the Eclipse Foundation governance model. The project codebase, issue tracking, and documentation are maintained in the open, and releases follow the processes defined by the Eclipse Foundation for open-source projects. This governance structure makes OpenMQ suitable for organizations that prefer community-driven, specification-based implementations for messaging infrastructure.

From a directory and taxonomy perspective, Eclipse OpenMQ fits into the categories of message-oriented middleware, JMS/Jakarta Messaging implementation, and Jakarta EE infrastructure (enterprise middleware). It is relevant wherever enterprises rely on JMS-compliant messaging for service integration, event distribution, and asynchronous processing in Java-based environments.