[Dev] [Architecture] WSO2 Message Broker 3.0.0 Alpha Released !

2015-09-01 Thread Sasikala Kottegoda 
WSO2 MB Team is pleased to announce the release of WSO2 Message Broker
3.0.0-Alpha2. You can now download the distribution which is available at
[1].

Following are the major changes applied in this version apart from the bugs
and fixes:

1. Removal of the support for Cassandra
2. Support for JMS local transactions

Bugs:

   - [MB-326 ] - OOM in MB 2.1.0 Beta
   When having more that 60 subscriptions
   - [MB-725 ] - When a node is
   killed, the queues which belog to the subscribers of the dead node are also
   removed
   - [MB-734 ] - NPE when browsing
   queue/topic messages sent by a C# JMS client
   - [MB-826 ] - Message can be resent
   when channel closed before acknowledgement is processed.
   - [MB-848 ] - Subscriber with
   permission to consume but doesn't have queue add, browse or delete
   permission failed to consume from queue
   - [MB-878 ] - Incompatibility with
   with AMQP Content header when using RabbitMQ publishers
   - [MB-889 ] - Display topic
   sections to an user who have only the login permissions
   - [MB-905 ] - created topic
   subscriptions not removed when running with jmeter
   - [MB-924 ] - broker.xml has to
   support Secure vault
   - [MB-940 ] - Observed "ERROR
   {org.wso2.andes.kernel.distruptor.inbound.InboundLogExceptionHandler} - [
   Sequence: 3884182 ] Exception occurred while processing inbound
   events.Event type: MESSAGE_EVENT", with a load test
   - [MB-972 ] - MQTT : Supporting
   Message Sizes Which Exceeds the Frame Size
   - [MB-993 ] - Subscriber Re
   Connection Causes Stability Issues
   - [MB-998 ] - An error is printed
   for each message when subscriber is disconnected while messages are
   publishing for MQTT
   - [MB-1025 ] - MQTT : Fix Message
   Size Limitation
   - [MB-1034 ] -
   ArrayIndexOutOfBoundsException when publishing MQTT messages while adding
   subscribers to same topic
   - [MB-1039 ] - MB doesn't support
   large messages for AMQP with MySQL datasource
   - [MB-1041 ] - Cassandra
   InvalidQueryException when durable subscriber goes offline
   - [MB-1052 ] -
   NullPointerException occurred in shutting down server when non durable
   subscription active
   - [MB-1053 ] - Warning log :
   Invalid State transition from DELETED suggested
   - [MB-1054 ] - MB server cannot
   restart after subscribe/publish messages to DSE cassandra
   - [MB-1058 ] - Message content not
   shown in the summary view
   - [MB-1063 ] - Browsing a queue
   which has 5 million messages is not possible to view
   - [MB-1065 ] - User with
   permission to browse queue messages is unable to browse the message
   - [MB-1066 ] - Messages are stuck
   in DB when the only publishing node is killed while publishing
   - [MB-1067 ] - Disable amqp
   protocol and publish / browse queue messages from console leads to dead page
   - [MB-1068 ] - When browsing queue
   messages pagination is shown for more than restricted number of messages
   - [MB-1069 ] - Can not delete a
   queue which has subscribed clients
   - [MB-1070 ] - MB 3.0.0 build with
   test fails on windows with "Failed to rename file wso2server.shas
   wso2server.sh"
   - [MB-1071 ] - Can not publish
   messages to a queue which is around 5mb in size
   - [MB-1073 ] - Unable to browse
   queues when large messages are present
   - [MB-1074 ] - Console allows to
   delete a queue while subscriber is consuming messages
   - [MB-1077 ] - MB does not start
   if the /etc/hosts file has multiple IP addresses for the host name
   - [MB-1079 ] - DLC is not being
   cleared when a queue is purged
   - [MB-1080 ] - Delete a queue from
   a tenant account and re-add the queue - popup says cannot create the queue
   - [MB-1082

Re: [Dev] [Architecture] WSO2 Message Broker 3.0.0 Alpha Released !

2015-09-01 Thread Sasikala Kottegoda 
Hi all,

Correction in the download link for the product. Use the link at [1] to
download WSO2 Message Broker 3.0.0-Alpha2

[1]
https://github.com/wso2/product-mb/releases/download/v3.0.0-ALPHA2/wso2mb-3.0.0-ALPHA2.zip

Thank you

On Tue, Sep 1, 2015 at 11:21 PM, Sasikala Kottegoda 
wrote:

>
> WSO2 MB Team is pleased to announce the release of WSO2 Message Broker
> 3.0.0-Alpha2. You can now download the distribution which is available at
> [1].
>
> Following are the major changes applied in this version apart from the
> bugs and fixes:
>
> 1. Removal of the support for Cassandra
> 2. Support for JMS local transactions
>
> Bugs:
>
>- [MB-326 ] - OOM in MB 2.1.0
>Beta When having more that 60 subscriptions
>- [MB-725 ] - When a node is
>killed, the queues which belog to the subscribers of the dead node are also
>removed
>- [MB-734 ] - NPE when browsing
>queue/topic messages sent by a C# JMS client
>- [MB-826 ] - Message can be
>resent when channel closed before acknowledgement is processed.
>- [MB-848 ] - Subscriber with
>permission to consume but doesn't have queue add, browse or delete
>permission failed to consume from queue
>- [MB-878 ] - Incompatibility
>with with AMQP Content header when using RabbitMQ publishers
>- [MB-889 ] - Display topic
>sections to an user who have only the login permissions
>- [MB-905 ] - created topic
>subscriptions not removed when running with jmeter
>- [MB-924 ] - broker.xml has to
>support Secure vault
>- [MB-940 ] - Observed "ERROR
>{org.wso2.andes.kernel.distruptor.inbound.InboundLogExceptionHandler} - [
>Sequence: 3884182 ] Exception occurred while processing inbound
>events.Event type: MESSAGE_EVENT", with a load test
>- [MB-972 ] - MQTT : Supporting
>Message Sizes Which Exceeds the Frame Size
>- [MB-993 ] - Subscriber Re
>Connection Causes Stability Issues
>- [MB-998 ] - An error is printed
>for each message when subscriber is disconnected while messages are
>publishing for MQTT
>- [MB-1025 ] - MQTT : Fix
>Message Size Limitation
>- [MB-1034 ] -
>ArrayIndexOutOfBoundsException when publishing MQTT messages while adding
>subscribers to same topic
>- [MB-1039 ] - MB doesn't
>support large messages for AMQP with MySQL datasource
>- [MB-1041 ] - Cassandra
>InvalidQueryException when durable subscriber goes offline
>- [MB-1052 ] -
>NullPointerException occurred in shutting down server when non durable
>subscription active
>- [MB-1053 ] - Warning log :
>Invalid State transition from DELETED suggested
>- [MB-1054 ] - MB server cannot
>restart after subscribe/publish messages to DSE cassandra
>- [MB-1058 ] - Message content
>not shown in the summary view
>- [MB-1063 ] - Browsing a queue
>which has 5 million messages is not possible to view
>- [MB-1065 ] - User with
>permission to browse queue messages is unable to browse the message
>- [MB-1066 ] - Messages are
>stuck in DB when the only publishing node is killed while publishing
>- [MB-1067 ] - Disable amqp
>protocol and publish / browse queue messages from console leads to dead 
> page
>- [MB-1068 ] - When browsing
>queue messages pagination is shown for more than restricted number of
>messages
>- [MB-1069 ] - Can not delete a
>queue which has subscribed clients
>- [MB-1070 ] - MB 3.0.0 build
>with test fails on windows with "Failed to rename file wso2server.shas
>wso2server.sh"
>- [MB-1071 ] - Can not publish
>messages to a queue which is around 5mb in size
>- [MB-1073 ] - Unable to browse
>queues when large messages are present
>- [MB-1074 ] - Console allows to
>delete a queue

[Dev] [Architecture] WSO2 Message Broker 3.0.0 Alpha Released !

2015-05-27 Thread Pumudu Ruhunage 
*WSO2 Message Broker 3.0.0 Alpha Released !*

WSO2 MB Team is pleased to announce the Alpha release of WSO2 Message
Broker 3.0.0. The distribution is available at [1].

This release adds following new features apart from bug fixes and
improvements.
1) Clean Session implementation for MQTT subscriptions.
2) Error based flow control implementation.
3) MQTT Retained topic feature for mb.

Following bug fixes, improvements and tasks have been fixed along with this
release.

Bug

   - [MB-391 https://wso2.org/jira/browse/MB-391] - Pagination does not
   work in Node List UI
   - [MB-450 https://wso2.org/jira/browse/MB-450] - [Intermittent] When
   sending a large number of messages and breaking the connection from time to
   time some messages do not get delivered.
   - [MB-623 https://wso2.org/jira/browse/MB-623] - Topic/Queue default
   role permissions are set to allow
   - [MB-662 https://wso2.org/jira/browse/MB-662] - Exception occurred
   while sending message out exception occurred as warning message
   - [MB-675 https://wso2.org/jira/browse/MB-675] - [Intermittent] NPE
   thrown when stopping the server
   - [MB-703 https://wso2.org/jira/browse/MB-703] - Durable Topic
   Subscriber does not receive messages when nodes are killed in cluster
   - [MB-704 https://wso2.org/jira/browse/MB-704] - Patch for event
   component has not committed
   - [MB-706 https://wso2.org/jira/browse/MB-706] - Default
   andes-config.xml of MB 2.2.0 includes malformed XML
   - [MB-741 https://wso2.org/jira/browse/MB-741] - Add secure vault
   support for Andes-virtualhost.xml file
   - [MB-755 https://wso2.org/jira/browse/MB-755] - Integrate log4j
   configurations for moquette to standard log4j.properties.
   - [MB-771 https://wso2.org/jira/browse/MB-771] - Should we start MQTT
   by Default?
   - [MB-797 https://wso2.org/jira/browse/MB-797] - Message redelivery
   with large queues blocks further message processing - in clustering mode
   - [MB-873 https://wso2.org/jira/browse/MB-873] - Durable topic cannot
   be deleted when subscriber is unsubscribed from UI
   - [MB-875 https://wso2.org/jira/browse/MB-875] - Unable to provide a
   hostname in broker.xml
   - [MB-905 https://wso2.org/jira/browse/MB-905] - created topic
   subscriptions not removed when running with jmeter
   - [MB-914 https://wso2.org/jira/browse/MB-914] - Getting errors while
   trying to shut down the MB cluster nodes which keeps idle for some time
   - [MB-917 https://wso2.org/jira/browse/MB-917] - Same durable topic
   subscriber shows on Active and Inactive Durable TopicSubscribers list
   - [MB-918 https://wso2.org/jira/browse/MB-918] - While trying to
   unsubscribe durable subscription, Observed ERROR
   {org.wso2.andes.server.protocol.AMQProtocolEngine} - Unexpected exception
   while processing frame.
   - [MB-946 https://wso2.org/jira/browse/MB-946] - Integration test
   cases failing
   - [MB-970 https://wso2.org/jira/browse/MB-970] - Hazelcast Instance
   not Active Exception when shutting down MB server.
   - [MB-974 https://wso2.org/jira/browse/MB-974] - Exceptions occur when
   closing server while having a active subscription
   - [MB-1003 https://wso2.org/jira/browse/MB-1003] - MQTT Published
   messages are not deleted from DB when subscriber is connected with QOS 2 in
   Cluster
   - [MB-1009 https://wso2.org/jira/browse/MB-1009] - When durable
   subscription is added with existing subscription ID entries are created for
   that subscription in registry
   - [MB-1019 https://wso2.org/jira/browse/MB-1019] - Add
   hazelcast.properties file to conf folder.
   - [MB-1020 https://wso2.org/jira/browse/MB-1020] - Publisher failover
   failed while gracefully shutting down MB node
   - [MB-1021 https://wso2.org/jira/browse/MB-1021] - Exception occurred
   in hazelcast while failover with gracefully shutting down
   - [MB-1027 https://wso2.org/jira/browse/MB-1027] - MQTT Concurrent
   Modification Exception throws while receiving topic messages
   - [MB-1028 https://wso2.org/jira/browse/MB-1028] - No retain option
   available in test framework mqtt publisher client
   - [MB-1031 https://wso2.org/jira/browse/MB-1031] - Durable subscribers
   do not get unsubscribed when unsubscribed through the 'Topic Subscriptions'
   window in management console
   - [MB-1035 https://wso2.org/jira/browse/MB-1035] - Intermittent MQTT
   test failure
   - [MB-1048 https://wso2.org/jira/browse/MB-1048] -
   performCleanSessionTestCase assertion failure

Improvement

   - [MB-171 https://wso2.org/jira/browse/MB-171] - Modify Username and
   Password Keeping for Message Store
   - [MB-432 https://wso2.org/jira/browse/MB-432] - Handle MB to
   Cassandra authentication internally
   - [MB-926 https://wso2.org/jira/browse/MB-926] - When Message store
   becomes unavailable MB should propagate that error outwards and show that
   information in GUI

Task

   - [MB-867 https://wso2.org/jira/browse/MB-867] - Implement MQTT
   Retain/Will Topic
   - [MB-868