Hi Hasitha, Thanks for creating the list. Make sure there are issues for each and make them L1.
It is two weeks when Shammi is back, so we will have to do these. Please start, and I will help when I can. --Srinath On Thu, Oct 11, 2012 at 11:37 PM, Hasitha Hiranya <[email protected]> wrote: > Considering all the Jiras, and my observations, following are the things > that should be done for MB 2.0 release. We need to prioritize and execute. > > - > /home/hasitha/carbonNew/carbon/platform/branches/4.0.0/products/mb/2.0.0/modules/samples/product/services/EventSinkService > cannot be built. > - > /home/hasitha/carbonNew/carbon/platform/branches/4.0.0/products/mb/2.0.0/modules/samples/service/pom.xml > needs updating. (https://wso2.org/jira/browse/MB-3) > - When publishing messages to a topic a queue is shown in UI - like "* > temp_*...". Should stop that. Reason is messages for a topic is stored > at Cassandra Global queue space. > - When two subscribers are there, topic messages are sent to both > subscriptions, but message counts are wrong (less than sent in both > subscribers.). This is a *major* issue. count is correct when there is > only one subscriber. > - Topics working with CEP seem to have problems still (as suho says.) > Needs looking into this. > - ESB 4.5.0 message store and processor does not work well with MB > 2.0. Message counts are very strange. > - When shutting down MB there are errors as Cassandra is down before > andes codes stop. And seems some errors are not cassandra related (proper > shutdown s needed for fail-over to work). > - Stop log growing when cassandra communication is down. > - Common SSL port (in carbon.xml and qpid-config both have this > config). > - BURL thing. > - Give a clean error message when Cassandra is down > - Update MB docs with MB 2.0 tuning parameters. > - Allowed max number of subscriptions configuration for a node. Is > this valid now? If it is print a warning when this is reached. And doc > updating (limitations) > - Test topics with esb. If there are errors fix them. > - I see a logging issue when andes client libs are put into ESB 4.5.0? > > As we are in final stage it is time we log only what is wanted and get rid > of all unwanted logs. I did this some time ago and now is seems it is > needed again. > Also need to add necessary informative logs and finalize it. > > Thanks. > > -- > *Hasitha Abeykoon* > Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * > * > * > > -- ============================ Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
