LibraryLink ToToggle FramesPrintFeedback

Introduction to the OpenWire Protocol

The OpenWire protocol is a JMS compliant wire protocol (defining message types and message encodings) that is native to the FUSE Message Broker. The protocol is designed to be fully-featured, JMS-compliant, and highly performant. It is the default protocol of the FUSE Message Broker.

Table 2.1 shows the transport protocols supported by the OpenWire wire protocol:


OpenWire supports a number of transport options, which can be set as query options on the transport URL. For example, to specify that error messages should omit the stack trace, use a URL like the following:

tcp://localhost:61616?wireformat.stackTraceEnabled=false

Where the wireformat.stackTraceEnabled property is set to false to disable the inclusion of stack traces in error messages. Table 2.2 gives the complete list of transport options for OpenWire.


FUSE Message Broker currently supports the following client types for the OpenWire protocol:

For details of how to program the messaging clients, see the FUSE Message Broker Client Guide.

If you want to develop an OpenWire client using other programming languages, try one of the following client types from the Apache ActiveMQ project:

  • C++ clients—for C++ clients, Apache ActiveMQ provides the CMS (C++ Messaging Service) API, which is closely modelled on the JMS specification. Only the TCP transport is supported for C++ clients.