WSO2 Message Broker 3.2.0

WSO2 Message Broker team is pleased to announce the release of WSO2 Message Broker 3.2.0!

WSO2 Message Broker is a 100% open source, distributed, highly scalable, portable, and interoperable product that supports JMS, AMQP and MQTT standards for enterprise messaging and can be used in scenarios where guaranteed message delivery is vital. It offers a flexible deployment model that supports single node execution to massively distributed execution. It provides a message brokering solution that enables asynchronous exchange of communications or publishing of messages for timely access by subscribers.

For more information on WSO2 Message Broker and to download the product please visit http://wso2.com/products/message-broker/. Also take a look at the online product documentation on https://docs.wso2.com/display/MB320/WSO2+Message+Broker+Documentation.

How to Run

1. Extract the downloaded zip
2. Go to the bin directory in the extracted folder
3. Run the wso2server.sh or wso2server.bat as appropriate
4. Launch a web browser and navigate to https://localhost:9443/carbon to access the admin console
5. Use "admin", "admin" as the username and password to login as an admin

WSO2 Message Broker 3.2.0 includes following improvements and bug fixes.

New Features

• MB-1686 - Message expiration (TTL)
• MB-1701 - Per message acknowledgements
• MB-1687 - Message re-delivery delay
• MB-1879 - Support XA Transactions

Bug Fixes

https://wso2.org/jira/issues/?filter=13677

Key Features of WSO2 Message Broker

• Standards Compliant, Portable, Interoperable Message Broker
• Support for JMS v1.0 and v1.1 API
• Advanced Message Queuing Protocol (AMQP) v0.91, a leading industry standard protocol for interoperable reliable messaging
• Supports MQTT protocol with support for all QoS levels and retained messaging
• Interoperability with many languages / platforms via AMQP clients for Java, .Net, C, C++, PHP, Ruby, Erlang and more
• Support for Distributed Queues
• Publishers and subscribers can connect to any broker
• Support for in-order reliable message delivery
• Support for strict and best effort (faster) delivery guarantees
• Support for dead letter channel
• Support for Publish/Subscribe Model (Topics)
• Publishers and subscribers can connect to any broker nodes
• Supports shared subscriptions

Management Console

• Console to manage the cluster and to view statistics about the cluster
• Support to browse publish/subscribe topics through management console
• Support to create, delete queues and browse queues using management console
• Support to display the messages inside a queue, send a messages to a queue, and purge the messages in the queue using management console

Manage & Monitor

• Comprehensive management & monitoring Web console with enterprise-level security
• Built-in collection and monitoring of standard access and performance statistics
• JMX MBeans for key metrics monitoring and management
• Flow control mechanism to control and safeguard from bursts of message loads
• User based authorization support for queues
• Role based authorization support for topics and users

Known Issues

All the open issues pertaining to WSO2 Message Broker are reported at the following location:
Known Issues

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.
Developer List : [email protected] | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature requests regarding WSO2 Message Broker through the public JIRA.

Support

We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

To learn more about WSO2 Message Broker and WSO2 support offerings please visit http://wso2.com/products/message-broker/.

-- The WSO2 Message Broker Team --

WSO2 Message Broker 3.2.0 RC2

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-RC2. Following are the bug fixes, improvements, and tasks that have been fixed along with this release.

Bug Fixes

• [MB-1910] - Fix intermittently failing xaStartJoinQueuePublishTestCase
• [MB-1927] - Recover test cases fail intermittently
• [MB-1929] - In performQueueSubscriptionsBreakAndReceiveTestCase messages are moved to DLC and not delivered to customers

WSO2 Message Broker 3.2.0 RC1

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-RC1. Following are the bug fixes, improvements, and tasks that have been fixed along with this release.

Bug

• [MB-1833] - Exception in long running tests while loading UI - Metrics - Postgresql
• [MB-1839] - [Intermittent] Observed a mismatch between the number of queue subscribers listed in the DB and the UI
• [MB-1894] - Invalid log message on channel message state transition
• [MB-1907] - Add message tracing for transactions
• [MB-1919] - Message acknowledgements received twice in fail-over
• [MB-1920] - Messages are not deleted after being acked in fail-over
• [MB-1921] - [DTX] connection/session close holding should be timed out
• [MB-1922] - NullPointerException when restoring an empty message in DLC queue
• [MB-1924] - java.util.Random is Not Needed
• [MB-1925] - [DTX] Cannot include two sessions from the same XAConnection in a distributed transaction
• [MB-1926] - Message acks duplicated when recovered

Improvement

• [MB-1870] - Need a INFO log when subscriber side flow control is enabled
• [MB-1881] - Cluster Events Missed - using RDBMS coordination

WSO2 Message Broker 3.2.0 BETA

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-BETA. Following are the bug fixes, improvements, and tasks that have been fixed along with this release.

Bug

• [MB-1645] - Durable topic subscription create queues in carbonsuper domain when the connection URL contains "clientID"
• [MB-1646] - There is a possible race condition in SlotDeliveryWorker Class
• [MB-1663] - Fix MB Issues with Multiple User stores
• [MB-1671] - SlotDeliveryWorker is not executing the assigned tasks
• [MB-1703] - Running JmsSelector Sample result warning in the wso2carbon log
• [MB-1711] - Getting a NullPointer when a consumer is closed without closing session
• [MB-1715] - Configuration issue in mqtt oauth
• [MB-1723] - Node ID is not set into Hazelcast map before "Member added" event arrives to a node.
• [MB-1727] - [Durable Subscription] When the db connectivity is dropped and reconnected durable topic subscription should be displayed as inactive
• [MB-1729] - Forbidden error when browsing the last message published via MC
• [MB-1732] - Disable queue subscription 'close' operation for non-owned nodes
• [MB-1734] - Error observed when messages moved to DLC
• [MB-1737] - With the current implementation of the moving messages from DLC can cause for an OOM issue.
• [MB-1738] - [Queue-Selectors] Some messages move to DLC, when multiple subscribers connected to the same queue via different cluster nodes
• [MB-1743] - Messages getting stuck after Forced restart
• [MB-1747] - Some messages getting stuck in the queue when the subscription owned node forcefully shutdown
• [MB-1750] - Null pointer exception during start up, when there are messages in DLC
• [MB-1753] - Messages re-routed/restored before its expiration time did not removed after the defined deletion time
• [MB-1754] - Expired messages when "expireMessagesInDLC = false" not getting delete when "expireMessagesInDLC = true"
• [MB-1755] - Expired messages not deleted from the queue
• [MB-1758] - Unable to close the queue subscriptions in a tenant domain
• [MB-1767] - [Durable Subscriptions] Expired messages in the DLC not deleted after defined time interval
• [MB-1769] - [Topics / Failover] Publisher class is unable to publish messages when a new coordinator is elected in MB cluster
• [MB-1770] - [Cluster / Coordinator] When stopping the coordinator node while messages are still publishing, a Hazelcast error is displayed
• [MB-1776] - Active durable subscriptions appeared under 'Inactive - durable subscription' list
• [MB-1780] - Queue/Topic subscriptions not enabled with the relevant permissions
• [MB-1781] - [Start up] A Nullpointer Exception occurred during the start up of MB node2
• [MB-1783] - [Tenant Domain] Un-acknowledged messages for durable topics appeared in the DLC of the carbon super user
• [MB-1786] - Nullpointer Exception observed when creating durable subscription with an existing subscription ID
• [MB-1792] - Queue Subscriptions failed when adding multiple queue subscribers to all cluster nodes
• [MB-1793] - [Unacked Messages] maxUnackedMessages value should not be hardcoded in backend
• [MB-1794] - [Intermittent] Nullpointer exception observed when queue subscriptions synced through cluster nodes
• [MB-1795] - [IndexOutOfBoundsException] Exception occurred while publishing and subscribing to a queue concurrently
• [MB-1797] - Exception in JMS client when retrieving the message count
• [MB-1798] - 'MixedDurableTopicTestCase' fails with an assert failure
• [MB-1800] - [Tenant / Durable Subscription] When creating a durable subscription for a tenant domain, permission denied error is displayed
• [MB-1801] - Created Topics subscribers missing in the subscriptions list
• [MB-1804] - [Hazelcast] Hazelcast error when stopping the node after starting with -Dsetup
• [MB-1806] - [RDBMS based coordination] Cordinator left the cluster throwing - Error detected while running coordination algorithm continuously
• [MB-1807] - [Cluster / Long running] One node has gone OOM in MB cluster while running publisher/subscriber for both Topic and Queues
• [MB-1808] - RDBMS connection is not closed in some methods
• [MB-1809] - Active durable topic subscribers are shown as active and inactive in management console
• [MB-1810] - [Cluster / Long running] Queues are not created at first in one node of the 3 node cluster
• [MB-1811] - [sporadic] All JobPoolThreads getting stuck after several AMQConnectionExceptions
• [MB-1814] - NullPointer Exception when shutting down the MB servers
• [MB-1815] - Although no active subscribers available topic cannot be deleted registry shows a entry of a subcription
• [MB-1816] - [Cluster / Long running] Some of the subscribers do not get created when execute the mixed subscriber script for Node1 Node2 in a clustered set up
• [MB-1819] - Refresh button failing for shared durable subscriptions
• [MB-1821] - Provided Inactive durable subscriber ID fails to retrieve the subscriber
• [MB-1822] - Issue when closing subscriber on failover
• [MB-1823] - Exception thrown when adding subscriptions
• [MB-1825] - [Durable Topics] Unable to search messages in DLC by its 'Destination' name
• [MB-1829] - NPE observed when restore/reroute expired messages from the DLC
• [MB-1832] - [GC Logs] GC logs are not created in repository/logs folder
• [MB-1835] - Exception thrown when syncing message routers in an RDBMS based cluster
• [MB-1840] - [Intermittent] ClassCastException when filtering durable subscription by ID
• [MB-1841] - Observed the below exception when shutting down the server
• [MB-1843] - [rdbmsBasedCoordination] On server startup MB throws - Internal error processing updateCurrentMessageIdForSafeZone
• [MB-1844] - Nullpointer thrown at startup and server stops if rdbmsBasedCoordination and networkPartitionsDetection is enabled
• [

WSO2 Message Broker 3.2.0 ALPHA2

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-ALPHA2. Following are the bug fixes, improvements, and tasks that have been fixed along with this release.

Bug

• [MB-1745] - MB cluster not performing due to thread-death errors
• [MB-1785] - [Topic Subscriptions] An empty page is displayed for topic subscriptions in management console
• [MB-1812] - [ESB + MB] Null pointer exception when publishing a message to publisher proxy for the first time
• [MB-1818] - Null pointer exceptions throwing from AndesSubscription class
• [MB-1847] - Permission denied in subscription failover
• [MB-1878] - Incorrect local subscription removal log printed when a node is killed

New Feature

• [MB-1879] - Distributed Transactions (XA) Support

Improvement

• [MB-1853] - Provide a way to dump message status to a file without direct accessing MBeans
• [MB-1867] - Add more debug level logs, info where necessary to the pub/sub authorization path of MB

WSO2 Message Broker 3.2.0 ALPHA

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-ALPHA. Following are the bug fixes, improvements and tasks that have been fixed along with this release.

Bug

• [MB-1325] - Messages not delivered even when there are matching subscribers with a mix of selection criteria
• [MB-1646] - There is a possible race condition in SlotDeliveryWorker Class
• [MB-1671] - SlotDeliveryWorker is not executing the assigned tasks
• [MB-1693] - MB server won't shutdown properly after an error occurs at startup on Mac (El Capitan)
• [MB-1703] - Running JmsSelector Sample result warning in the wso2carbon log
• [MB-1716] - Null pointer exception is thrown when an unauthenticated client is subscribing to mqtt topic
• [MB-1717] - Meaningful identifier for subscriptions
• [MB-1719] - Subscriptions list should be able to sort and searched
• [MB-1723] - Node ID is not set into Hazelcast map before "Member added" event arrives to a node.
• [MB-1746] - Fix SubscriptionDeleteTestCase
• [MB-1750] - Null pointer exception during start up, when there are messages in DLC
• [MB-1759] - Filtering subscriptions not working in the paginated window
• [MB-1761] - [Durable Subscriptions] Clicking on unsubscribe link for inactive durable subscriptions should remove the subscription
• [MB-1778] - Cluster wide All connected nodes filtering not working & dropdown issue
• [MB-1789] - [Oracle SQL] Observed message loss in queues
• [MB-1790] - Active durable subscription not shown when filtered from the subscrption identifier

Improvement

• [MB-1634] - Add a warning if Slot Deletion Safe Zone is not Moving
• [MB-1662] - Allow to configure number of reserved db connections for Publisher transactions
• [MB-1672] - Remove settable futures from inbound event handling path
• [MB-1704] - Implement RDBMS based cluster notification synchronization
• [MB-1708] - Implement RDBMS based coordinator election algorithm
• [MB-1762] - [JMX] Some of the attributes in MBeans does not get listed in DAS

New Feature

• [MB-1764] - Subscription Filtering and Pagination for Topic and Queue subscriptions

Task

• [MB-1771] - Document Subscription Filtering Feature

WSO2 Message Broker 3.2.0 M3

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-M3. Following are the bug fixes, improvements and tasks that have been fixed along with this release.

Bug

• [MB-1683] - MB goes OOM (with compression enabled) with MSSQL as message store
• [MB-1705] - WSO2 MB cannot start on IBM JDK 1.8
• [MB-1709] - make broker.xml used shared durable testcase and other files upto date
• [MB-1710] - Unable to create subtopics in specific scenarios
• [MB-1712] - User who has ADD permission cannot create sub topic
• [MB-1720] - Cannot create topic by authorized user where previously created by admin but already deleted
• [MB-1724] - Cannot enable message tracer from the UI - Intermittent
• [MB-1730] - [Version] On startup it shows as Message Broker 3.1.0 in version 3.2.0

Improvement

• [MB-1662] - Allow to configure number of reserved db connections for Publisher transactions
• [MB-1672] - Remove settable futures from inbound event handling path
• [MB-1748] - Allow the same value to be used for both connectionfactory.QueueConnectionFactory and connectionfactory.TopicConnectionFactory in jndi.properties when secure vault is enabled

WSO2 Message Broker 3.2.0 M2

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-M1. Following are the bug fixes, improvements and tasks that have been fixed along with this release.

Bug

• [MB-1659] - Thread leak in SocketConnectorIoProcessor when andes client connection timeout
• [MB-1702] - Message Expiration in DLC is not working

New Feature

• [MB-1686] - Support TTL

WSO2 Message Broker 3.2.0 M1

WSO2 MB Team is pleased to announce the release of WSO2 Message Broker 3.2.0-M1. Following are the bug fixes, improvements and tasks that have been fixed along with this release.

Bug

• [MB-524] - messageIDs are dumped on logs when rerouting messages
• [MB-1665] - Message Compression (in broker.xml) is not working for durable subscriptions
• [MB-1684] - Topic couldn't get subscribed if email username enabled
• [MB-1696] - Dead lock when subscriptions added during network partition
• [MB-1697] - Unable to browse messages in DLC.
• [MB-1698] - Inactive shared durable subscriptions after several network partition scenarios.

Improvement

• [MB-1573] - Display supported message headers in MC
• [MB-1695] - Increase the String length allowed in a JMS Map Message

New Feature

• [MB-1687] - Message retry delay
• [MB-1699] - Set destination name as a JMS message property for each message.
• [MB-1701] - Per Message Acknowledgement Mode

WSO2 Message Broker 3.1.0

WSO2 Message Broker team is pleased to announce the release of WSO2 Message Broker 3.1.0!

WSO2 Message Broker is a 100% open source, distributed, highly scalable, portable, and interoperable product that supports JMS, AMQP and MQTT standards for enterprise messaging and can be used in scenarios where guaranteed message delivery is vital. It offers a flexible deployment model that supports single node execution to massively distributed execution. It provides message brokering solution that enables asynchronous exchange of communications or publishing of messages for timely access by subscribers.

For more information on WSO2 Message Broker and to download the product please visit http://wso2.com/products/message-broker/. Also take a look at the online product documentation on https://docs.wso2.com/display/MB310/WSO2+Message+Broker+Documentation.

How to Run

1. Extract the downloaded zip
2. Go to the bin directory in the extracted folder
3. Run the wso2server.sh or wso2server.bat as appropriate
4. Launch a web browser and navigate to https://localhost:9443/carbon to access the admin console
5. Use "admin", "admin" as the username and password to login as an admin

WSO2 Message Broker 3.1.0 includes following improvements and bug fixes.

New Features

MB-1588 - Forcefully Delete Subscriptions
MB-1592 - Support for PostgreSQL as the Message Store

Bug Fixes

https://wso2.org/jira/issues/?filter=12639

Improvements

https://wso2.org/jira/issues/?filter=12640

Key Features of WSO2 Message Broker

Standards Compliant, Portable, Interoperable Message Broker

Support for JMS v1.0 and v1.1 API
Advanced Message Queuing Protocol (AMQP) v0.91, a leading industry standard protocol for interoperable reliable messaging
Supports MQTT protocol with support for all QoS levels and retained messaging
Interoperability with many languages / platforms via AMQP clients for Java, .Net, C, C++, PHP, Ruby, Erlang and more

Support for Distributed Queues

Publishers and subscribers can connect to any broker
Support for inorder reliable message delivery
Support for strict and best effort (faster) delivery guarantees
Support for dead letter channel

Support for Publish/Subscribe Model (Topics)

Publishers and subscribers can connect to any broker nodes
Supports shared subscription

Management Console

Console to manage the cluster and to view statistics about the cluster
Support to browse publish/subscribe topics through management console
Support to create, delete queues and browse queues using management console
Support to display the messages inside a queue, send a messages to a queue, and purge the messages in the queue using management console

Manage & Monitor

Comprehensive management & monitoring Web console with enterprise-level security
Built-in collection and monitoring of standard access and performance statistics
JMX MBeans for key metrics monitoring and management
Flow control mechanism to control and safeguard from bursts of message loads
User based authorization support for queues
Role based authorization support for topics and users

Known Issues

All the open issues pertaining to WSO2 Message Broker are reported at the following location:
Known Issues

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.
Developer List : [email protected] | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature requests regarding WSO2 Message Broker through the public JIRA.

Support

We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

To learn more about WSO2 Message Broker and WSO2 support offerings please visit http://wso2.com/products/message-broker/.

-- The WSO2 Message Broker Team --