MQTT is a light weight event and message oriented protocol allowing devices to asynchronously communicate efficiently across constrained networks to remote systems, standardized by OASIS. FioranoMQ 10.2.0 supports the MQTT Protocol (the 3.1.1 standard version) which can be run simultaneously with the JMS Server. MQTT uses the Publish/Subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
The MQTT protocol embedded in the FioranoMQ Server uses the same Topic destinations as FioranoMQ and automatically maps MQTT clients and JMS clients. Therefore, a Topic destination can concurrently host MQTT/JMS Publishers and Subscribers. An MQTT packet is converted to a JMS BytesMessage to be consumed by a JMS Subscriber, and a JMS messages is converted to an MQTT packet to be consumed by an MQTT Subscriber as required.
The newly added MQTT Protocol supports only clients of version 3.1.1 and ia is not backward compatible with 3.1 standards based MQTT clients.
Handling FioranoMQ Database Corruption
In this latest release, Database corruptions (when detected) are narrowed down to a specific destination and backed up for further analysis and recovery. A new destination with the same name now replaces the corrupted destination at runtime and clients are automatically connected to the fresh destination.
The FioranoMQ Web console has been enhanced to monitor the corrupted destinations under the Queues/Topics tab and the provision to execute recovery and replay commands on the corrupted destinations.
Server Thread dumps
In order to provide more information on the worker threads in the Server, Thread stack traces are dumped to the log files for client requests taking more than the configured interval of time. This feature helps in identifying bottle necks and execution delays in the server.
Pubsub Message Browser support has been added to Native C++ RTL as well as the older C++ RTL.
Additional information on client connections has been added to determine the FioranoMQ version, build number, and the Protocol used by each client connection. These can be viewed from the web console's connections tab.
New JMX APIs are added to Queue and PubSub services to get the number of deliverable messages and undeleted messages count for Persistent and Non-Persistent messages separately.