Hi Indunil, As I understand, "FOREIGN KEY constraint violation" issue is a regression issue therefore the deadlock issue cannot be resolved until foreign key constraint violation issue is fixed, right?
Thank you. On Thu, Oct 1, 2015 at 2:01 PM, Indunil Upeksha Rathnayake <indu...@wso2.com > wrote: > Hi, > The deadlock issue in https://wso2.org/jira/browse/MB-1326 is resolved in > both oracle 12c and 11g r2. (Please refer previous mails in this mail > thread to get the idea of the issue). Then after a "FOREIGN KEY constraint > violation" issue occurred in both mssql and oracle, intermittently (Refer > the attached file "errorLog_foriegnKeyViolation" for the error log). For > that, issued the fix in https://github.com/wso2/carbon-kernel/pull/512, > and it worked for oracle, but not for mssql. This is tested in following > scenarios in MB cluster. > > 1. 5 queues - 5 subscribers and 5 consumers ( 1 publisher and 1 consumer > each ) > 2. 5 Topics - 5 subscribers and 5 consumers ( in mssql, it breaks for this > scenario) > 3. 100 topics - 100 publishers and 100 consumers ( 1 publisher and 1 > consumer each ) > 4. 1 topic - 100 subscribers / 100 consumers > 5. Mixed scenario where multiple queues, topics and durable topics are used > > I have attached all the debug logs here. Please consider this matter and > provide your feedbacks on resolving this. > > Thanks and Regards > -- > Indunil Upeksha Rathnayake > Software Engineer | WSO2 Inc > Email indu...@wso2.com > > -- *Manuri Amaya Perera* *Software Engineer* *WSO2 Inc.* *Blog: http://manuriamayaperera.blogspot.com <http://manuriamayaperera.blogspot.com>*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
