[ https://forge.continuent.org/jira/browse/SEQUOIA-732?page=all ] Ralph Hannus closed SEQUOIA-732: --------------------------------
This has been tested. > The Deadlock detection thread can loop generating invalid abort requests > ------------------------------------------------------------------------ > > Key: SEQUOIA-732 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-732 > Project: Sequoia > Type: Bug > Components: Core > Versions: Sequoia 2.9 > Reporter: Ralph Hannus > Assignee: Ralph Hannus > Fix For: Sequoia 2.10 > > > When the head of the conflicting queue does not change immediately after an > abort has been issued to clear a deadlock, the DeadlockDetectionThread will > issue another abort request. This can result in a flood of the following > messages: > 2006-07-20 08:39:35,359 INFO sequoia.controller.loadbalancer Deadlock > detected on backend specdb02-1, aborting transaction 28691 > 2006-07-20 08:39:35,359 WARN controller.RequestManager.specdb02 No > transaction metadata found to abort transaction 28691. Creating a fake > context for abort. > 2006-07-20 08:39:35,359 WARN controller.RequestManager.specdb02 No > transaction metadata found to abort transaction 28691. Creating a fake > context for abort. > The DeadlockDetectionThread should wait before issuing a second abort request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
