Hi all, I tested the following scenarios in a WSO2 MB cluster with MSSQL as the message store.
- Multiple publisher, consumer scenarios with single queue - Multiple publisher, consumer scenarios with single topic - Multiple publisher, consumer scenarios with single durable topic subscriber - Multiple publisher, consumer scenarios with multiple queues - Multiple publisher, consumer scenarios with multiple topics - Multiple publisher, consumer scenarios with multiple durable topic subscribers - Hierarchical topic subscribers on multiple nodes [+] Stable - go ahead and release On Sat, Nov 7, 2015 at 2:42 PM, Pumudu Ruhunage <pum...@wso2.com> wrote: > Hi all, > > I tested following MQTT scenarios in a MB cluster. > > - Multiple subscriber scenarios > - Multiple publisher scenarios > - Mixed Multiple publisher/subscriber scenarios > - Single topic 5 subscribers and 5 publishers > - 5 topics 5 subscribers and 5 publishers (1 topic per subscriber > and publisher) > - Multiple topics 5 subscribers and 5 publishers > - Clean session true scenarios > - Clean session false scenarios > - QOS levels basic test scenarios. Following QOS levels covered. > - QOS 0 > - QOS 1 > - QOS 2 > - Hierarchical topics and Wildcard scenarios > - Tenant level security - basic scenarios > - Retain topic scenarios > > Did not encounter issues. > Thus +1. Stable - go ahead and release. > > Thanks, > Pumudu > > On Sat, Nov 7, 2015 at 2:21 PM, Hasitha Hiranya <hasit...@wso2.com> wrote: > >> Hi all, >> >> I tested the following scenarios in a MB cluster >> >> >> - multiple publisher multiple consumer - queues >> - multiple publisher multiple consumer - topics >> - multiple publisher multiple consumer - durable topic shared >> - multiple publisher multiple consumer - queues - with subscription >> break in middle >> - hierarchical topic subs - subscribers on multiple nodes >> - topics with wildcards (* and #) - subscribers on multiple nodes >> >> >> Did not encounter issues >> Thus +1. Stable - go ahead and release >> >> Thanks >> >> On Sat, Nov 7, 2015 at 3:28 AM, Akalanka Pagoda Arachchi < >> darsha...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> This is the second release candidate of WSO2 Message Broker 3.0.0. >>> >>> This release fixes the following issues: >>> https://wso2.org/jira/issues/?filter=12508 >>> >>> <https://wso2.org/jira/issues/?filter=12422> >>> Please download, test and vote. >>> >>> Source & binary distribution files: >>> https://github.com/wso2/product-mb/releases/tag/v3.0.0-RC2 >>> >>> Maven staging repo: >>> http://maven.wso2.org/nexus/content/repositories/orgwso2mb-118/ >>> >>> The tag to be voted upon: >>> https://github.com/wso2/product-mb/tree/v3.0.0-RC2 >>> >>> >>> [+] Stable - go ahead and release >>> [-] Broken - do not release (explain why) >>> >>> Thanks and Regards, >>> MB Team. >>> >>> -- >>> *Darshana Akalanka Pagoda Arachchi,* >>> *Software Engineer* >>> *078-4721791* >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Hasitha Abeykoon* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Pumudu Ruhunage > Associate Software Engineer | WSO2 Inc > M: +94 779 664493 | http://wso2.com > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Asanka Abeyweera Software Engineer WSO2 Inc. Phone: +94 712228648 Blog: a5anka.github.io
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
