This documentation is for WSO2 Message Broker 3.0.0. View documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

What's new in this release

WSO2 Message Broker version 3.0.0 is the successor of version 2.2.0. It is based on the Carbon platform version 4.4.2. It contains the following new features and enhancements:

  • Databases can be configured for storage using different database types. The supported database types in this release are H2, MySQL, MSSQL and Oracle. Note that Cassandra has been removed. For more information see the topic on setting up the MB database.
  • If your enterprise already has a JDBC store, the minimum number of nodes required for setting up a WSO2 Message Broker cluster is two nodes. It is no longer required to have nine JVMs for an MB cluster.
  • MQTT (Message Queuing and Telemetry Transport), a lightweight, broker-based publish/subscribe messaging protocol allows the queues and topics to be globalised as well as scaled across several instances. Read more about MQTT in MB.
  • New message distribution algorithm for distributed subscribers over a cluster. For more information read about slot-Based architecture in MB.
  • Error, warning and reporting improvements on the management console.
  • Support for metrics visualization. For more information see the topic on working with Carbon metrics.

Fixed and known issues

  • WSO2 Message Broker 3.0.0 - Fixed Issues
  • WSO2 Message Broker 3.0.0 - Known Issues
  • No labels