What are the protocols supported by Fuse Message Broker for the clients which connect to it?
Environment
Fuse Message Broker 5.x
Issue
What are the protocols supported by Fuse broker for the clients which connect to it?
What protocols are used by the clients to connect to Fuse broker?
Resolution
Fuse broker supports connections with a host of different clients. It provides support for both OpenWire and STOMP encoding formats.OpenWire
The default wire protocol used by native Java FUSE Message Broker clients is the OpenWire binary format. There are also OpenWire client libraries available for C, C++ and .NET.
There is official support for non java clients. This is via NMS (.Net Api) and CMS (C++ Api).
Streaming Text Oriented Messaging Protocol (STOMP) is used to support FUSE Message Broker clients written in languages such as Ruby, Perl, Python, and PHP. We support issues with the stomp transport. So we provide commercially reasonable effort to investigate those. If the issue is broker side, we will fix it. If its with the client, it's not officially supported.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments