Hi All, +1 for removing H2 in-memory mode. Currently we have to maintain RDBMS table structure in code base[1][2] (jira[3]) because H2 in-memory db. Which is not a best practice. There are some complications in test framework as well when running in-memory tests[4].
@yasassri, I think this[5] jira is a duplicate with this one[6]. [1] org.wso2.andes.store.rdbms.h2.H2MemMessageStoreImpl [2] org.wso2.andes.store.rdbms.h2.H2MemAndesContextStoreImpl [3] https://wso2.org/jira/browse/MB-1023 [4] https://wso2.org/jira/browse/MB-992 [5] https://wso2.org/jira/browse/MB-1158 [6] https://wso2.org/jira/browse/MB-1310 Thanks, On Fri, Sep 18, 2015 at 9:54 AM, Yasassri Ratnayake <[email protected]> wrote: > Hi Asitha, > > I just did some basic tests and came across following issues. Since we are > not recommending H2 for production, Is there any added advantage of > maintaining this feature? > > [1] - https://wso2.org/jira/browse/MB-1310 > [2] - https://wso2.org/jira/browse/MB-1318 > [3] - https://wso2.org/jira/browse/MB-1312 > > With Regards, > > On Fri, Sep 18, 2015 at 5:23 AM, Asitha Nanayakkara <[email protected]> > wrote: > >> Hi Yasassri, >> >> If I'm not mistaken, H2 In memory store is simply using the existing >> RDBMS message store implementations. The difference is the database >> connection (In memory store connect to an H2 in-memory database). Therefore >> this doesn't support clustered setup. >> >> What are the critical bugs encountered? >> >> Regards, >> Asitha >> >> >> On Thu, Sep 17, 2015 at 11:44 PM, Yasassri Ratnayake <[email protected]> >> wrote: >> >>> Hi All, >>> >>> Currently MB 3.0 has the capability of utilizing H2's In memory database >>> feature for persisting messages. But after doing a simple smoke test on >>> this feature I found several critical bugs. So we should fix these blocking >>> issues before the release. IMHO, due to strict time constraints on MB >>> release it is ideal to remove this feature from this release rather than >>> shipping this with bugs. (MB team has many more critical issues to fix) >>> Some customers may try to use this feature. If so we are asking for trouble. >>> >>> WDYT? >>> >>> With Regards, >>> >>> -- >>> Yasassri Ratnayake >>> Software Engineer - QA >>> WSO2 Inc ; http://wso2.com >>> lean.enterprise.middleware >>> *Mobile : +94715933168 <%2B94715933168>* >>> *Blogs : http://yasassriratnayake.blogspot.com >>> <http://yasassriratnayake.blogspot.com/>* >>> * http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>* >>> >> >> >> >> -- >> *Asitha Nanayakkara* >> Software Engineer >> WSO2, Inc. http://wso2.com/ >> Mob: + 94 77 85 30 682 >> >> > > > -- > Yasassri Ratnayake > Software Engineer - QA > WSO2 Inc ; http://wso2.com > lean.enterprise.middleware > *Mobile : +94715933168 <%2B94715933168>* > *Blogs : http://yasassriratnayake.blogspot.com > <http://yasassriratnayake.blogspot.com/>* > * http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
