Hi, Did not we increment queue count together with message storing, as a combined call to Cassandra database? AFAIR we did. How did it add an additional cost?
If we periodically update queue count we have to be aware of usability issues. What abt, 1. Always keep queue count in memory. 2. We store it whenever MB shuts down (additionally we can store message count time to time in leisurely manner) 3. We read it whenever MB startup. 4. Whenever message count is wanted for operations read it from memory. During a crash we might loose track of exact number of messages by the way. Thanks. On Fri, Aug 30, 2013 at 2:42 PM, Malinga Purnasiri <[email protected]>wrote: > hi Ishara, > > As i remember since per message count increment to DB kill the performance > of MB considerably; we all thought of removing it for the moment. With the > new disruptor changes we thought of updating queue count periodically (not > in real-time). So i think its not good idea to depend on the queue count > for the purging operation. instead .. > > What if we use [1] receive(timeout). We can set the timeout to (may be) 5 > secs. > > Any ideas ? > > [1] > http://docs.oracle.com/javaee/1.4/api/javax/jms/MessageConsumer.html#receive(long) > > > > > On Wed, Aug 28, 2013 at 2:01 PM, Ishara Premadasa <[email protected]> wrote: > >> Hi, >> >> Since we have removed the message counters after introducing the >> disruptor based message processing for MB 2.1.1 both the above features >> are currently not working and we are trying to fix this. As the previous >> MessageWriter, implementations from 2.1.0 are no longer used, now we don't >> keep message counts stored in Cassandra so the counters are always shown as >> zero. Due to this the current queue purge feature has too broken since it >> periodically checks the message counter and performs purge operation >> continuously till the total message count in the queue is zero. >> >> IMO we need to find an alternative way to get message counters work in >> the queue as the message writers are not used now. If not we may need to >> remove these two features from UI, since purging too depending on the >> counters. >> >> Thanks! >> Ishara >> >> -- >> Ishara Premasada >> Software Engineer, >> WSO2 Inc. http://wso2.com/ >> *Blog : http://isharapremadasa.blogspot.com/ >> Twitter : https://twitter.com/ishadil >> Mobile : +94 714445832* >> >> >> > > > -- > Malinga Pathmal, > Technical Lead, WSO2, Inc. : http://wso2.com/ > Phone : (+94) 715335898 > -- *Hasitha Abeykoon* Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
