On Sun, May 22, 2011 at 11:20 AM, Hasini Gunasinghe <has...@wso2.com> wrote:
> > > On Sun, May 22, 2011 at 11:01 AM, Senaka Fernando <sen...@wso2.com> wrote: > >> Hi Hasini, >> >> On Sun, May 22, 2011 at 7:14 AM, Hasini Gunasinghe <has...@wso2.com>wrote: >> >>> Hi, >>> >>> On Sat, May 21, 2011 at 9:19 PM, Thilina Buddhika <thili...@wso2.com>wrote: >>> >>>> We have one L1 to fix from the security side and Hasini is working on >>>> it. >>> >>> >>> The reported L1 [1] issue is not an issue of user-core, as I understood >>> while reproducing it. >>> >>> AFAIU, it is due to the server startup script not facilitating this kind >>> of a scenario in a straight forward manner. But it can be overcome by >>> workarounds as I have mentioned in the comment to the issue. >>> >>> Can you please review the comment and advice what should be done to this >>> L1? >>> >> >> Thanks Senaka for the explanation. > > Yes, this is an issue from UM core. The thing is the UM core does not >> test the existence of the DB before running the -Dsetup script. In Registry >> Kernel, we check for the existence of the DB by running this query, SELECT >> REG_PATH_ID FROM REG_PATH WHERE REG_PATH_VALUE='/'. >> >> You need to do something similar, which you have done, "SELECT * FROM >> UM_USERS". But, in this scenario, it seems to be failing for some reason. >> Can you check why that fails during the start-up of the second server? >> > > As I understood, start up of the second server fails because when it is > started with -Dsetup, db script is run in the UM_DB where tables are already > created and some initial values are added by the first server. > >> >> Now, that's part 1 of this fix. Part 2, is bit tricky. If you check the >> h2.sql, you'll notice that there are "IF NOT EXISTS" for each creation. But, >> in mysql.sql, some do not have it. I don't know the exact reasons for that, >> but it seems to be another issue that leads to this. >> > > I will look more into this according to what you have mentioned. > Had a look into this again, and part 2, should not be related in this case. You need to check what makes the execution of "SELECT * FROM UM_USERS" fail with an SQLException which is what makes UM core, attempt to recreate the Database. Thanks, Senaka. > > Thanks, > Hasini. > >> >> Thanks, >> Senaka. >> >>> >>> [1]https://wso2.org/jira/browse/CARBON-9881 >>> >>> Thanks, >>> Hasini. >>> >>>> >>>> Thanks, >>>> Thilina >>>> >>>> On Fri, May 20, 2011 at 11:34 AM, Afkham Azeez <az...@wso2.com> wrote: >>>> >>>>> Folks, >>>>> What is the plan to address these? Are people working on these L1s? >>>>> After the branching, you have to make sure that the fixes are committed to >>>>> the trunk as well as the branch. The proper process is, to fix this in the >>>>> trunk, create a patch and attach it to the Jira, and then commit that >>>>> patch >>>>> to the trunk. Please follow that process. >>>>> >>>>> Thanks >>>>> Azeez >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>> twitter: >>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> Carbon-dev@wso2.org >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thilina Buddhika >>>> Associate Technical Lead >>>> >>>> WSO2 Inc. ; http://wso2.com >>>> lean . enterprise . middleware >>>> >>>> phone : +94 77 44 88 727 >>>> blog : http://blog.thilinamb.com >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2 Inc.; http://wso2.com >> * >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
