Hi Isuruwan, Thanks for the suggestion I will look at mysql logs for this.
Regards, Malith On Sat, Oct 3, 2015 at 7:29 PM, Isuruwan Herath <isuru...@wso2.com> wrote: > Hi Malith, > > From the log it seems some thread is holding a table lock, which prevents > to acquire the lock when the executing the update command to the resource > content id. Check the process list from mysql and identify the thread which > is holding the lock. If that is a legitimate concurrent operation in app > cloud which is taking a long time to execute, then try increasing the > innodb lock wait time out. > > HTH, > Isuruwan > > On Thu, Oct 1, 2015 at 11:17 AM, Malith Munasinghe <mali...@wso2.com> > wrote: > >> Hi All, >> >> Recently on app cloud we faced an locked timeout exceeded issue on >> registry. This kept application creation down for a while. Is there any >> suggestions on how to keep these kind of issues from occurring. >> >> Attached is the error log that was observed. >> >> Regards, >> Malith. >> >> -- >> Malith Munasinghe | Software Engineer >> M: +94 (071) 9401122 >> E: mali...@wso2.com >> W: http://wso2.com >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Isuruwan Herath > Technical Lead > > Contact: +94 776 273 296 > -- Malith Munasinghe | Software Engineer M: +94 (071) 9401122 E: mali...@wso2.com W: http://wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
