awsome idea. lets do that. On Tue, Jan 27, 2015 at 4:36 PM, Hasitha Hiranya <hasit...@wso2.com> wrote:
> For example following scenario should be testable. At least check message > counts after sending to DLC/deleting/purging operations > > 1) Send couple of messages to MBQ1 queue. Make these messages end up in > DLC > > 2) Disable the JMS consumer and send messages so that there will be > message in MBQ1 queue. > > 3) Purge the MBQ1 ( so that messages in DLC and MBQ1 will be cleared) > > 4) Send messages to MQ1 again ... > > 5) Enable JMS Consumer (this will put messages to dlc again) > > 6) Browse the Queue you will see there are message in DLC and the queue > and verify queue count=0 dlc count = x > > On Tue, Jan 27, 2015 at 9:01 PM, Hasitha Hiranya <hasit...@wso2.com> > wrote: > >> Hi, >> >> We need to be careful with message count display in UI in MB 3.0.0. >> >> For most of users this is the first impression about the product. If >> message counts are wrong and unpredictable, even for us developers, it is >> hard to isolate issues. >> >> Thus in the test suite via admin services we should be able to query the >> message count after doing some message publish/ consume. >> >> We need to add some tests (or do this at the end of each existing test >> standalone and cluster) checking message count and verify. >> >> Thanks >> >> -- >> *Hasitha Abeykoon* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> > > > -- > *Hasitha Abeykoon* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
