Thanks Hasitha and Ramith! Adding Rukshani and Sam from the docs team. Regards, Tania
On Tue, Dec 16, 2014 at 12:03 AM, Ramith Jayasinghe <[email protected]> wrote: > Good stuff! lets create a L1 (for docs team) stating that we need to have > time synced in servers (in clustering guide). > Otherwise we will miss it! > > On Mon, Dec 15, 2014 at 11:46 PM, Hasitha Hiranya <[email protected]> > wrote: >> >> Hi, >> >> I did following change to topic subscriptions. >> >> 1. say sub 1 subscribed to topic x. >> 2. say sub 2 subscribed to topic x. >> 3. say 10,000 msgs published to topic x. >> >> Now when sub 1 is closed and resubscribe, it should get no messages. >> This is now done comparing time stamps of subscription and message >> arrival time. >> >> This brings the need that all MB nodes MUST BE TIME SYNCED. >> >> Standalone Test case also added. >> >> Note that when all topic subscribers vanished from node, underlying >> storage queue is purged. >> >> A test case is added for this as well. >> >> Also added abt 10 durble topic test cases. >> >> Verified that all these pass in current MB 3.0.0 SNAPSAHOT. >> >> Thanks >> >> -- >> *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: [email protected] > P: +94 777542851 > > -- Tania Mahanama Senior Technical Writer Contact: Mob: +94 077 5129270
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
