[ https://forge.continuent.org/jira/browse/SEQUOIA-1026?page=comments#action_14316 ]
Andrew Lawrenson commented on SEQUOIA-1026: ------------------------------------------- I'm seeing a potentially serious problem from this. As mentioned before, DriverCompliance.complianceTest() is leaving it's connection open. In my scenario (Sequoia 2.10.9, using Apache Derby), what this means is that at startup, when this is called, many (>100) shared locks are left over the system tables (I think this is from the use of getMetaData()). This prevents (for example) adding a new table - I get a lock timeout, as the call to getMetaData has been executed with Serializable isolation & has left shared locks on the rows it has read, so the call to add table cannot get the exclusive lock it needs to add a new entry. Having DriverCompliance.complianceTest() commit when it finishes removes these locks, and everything works fine. > Test connection statements are not properly closed > -------------------------------------------------- > > Key: SEQUOIA-1026 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-1026 > Project: Sequoia > Type: Bug > Components: Core > Versions: Sequoia 2.9 > Reporter: Pierre Besson-Deblon > Priority: Minor > > Original Estimate: 30 minutes > Remaining: 30 minutes > > Many test connection statements are opened and not explicitly closed. > Those statements could live for a long time depending on SGBD. -- 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
