Hi Denis, I worked on your test results. Most of the errors seems to be due to Hibernate/C3PO and not to Sequoia. One error seems to be a problem with SQL Server (foreign key definition). I created 2 JIRA issues for the problems related to Sequoia and attached patches to fix them.
Here is the complete analysis (only tests with errors): [junit] Running org.hibernate.test.abstractembeddedcomponents.cid.AbstractCompositeIdTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 46,89 sec the connection seems to be closed java.sql.SQLException: [EMAIL PROTECTED] has been closed() you can no longer use it I found these two topics on hibernate forums which seems related to this problem: http://forum.hibernate.org/viewtopic.php?t=934779 http://forum.hibernate.org/viewtopic.php?p=2294989 It doesn't seem to be a Sequoia problem. [junit] Running org.hibernate.test.abstractembeddedcomponents.propertyref.AbstractComponentPropertyRefTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 11,297 sec There are in fact 2 errors. The first one is: 19:40:44,578 ERROR SchemaExport:275 - Message of cause: write request 11 failed: Backend VirtualDatabase - BackendWorkerThread for backend 'mainPCDB' with RAIDb level:1 failed (There are no primary or candidate keys in the referenced table 'ADDRESS' that match the referencing column list in the foreign key 'FK91952343862BE88A'.) -> it's an error message of SQL Server and not one of Sequoia so I suppose it's a SQL Server problem (can you check that you also have this error with SQL Server only?) The second one is the same error than above with the connection. [junit] Running org.hibernate.test.array.ArrayTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 33,968 sec Message of cause: Unknown table '' in this INSERT statement: 'insert into aaa default values' The default values syntax was not supported by the InsertRequest parsing code. I created https://forge.continuent.org/jira/browse/SEQUOIA-909 and attached a patch to fix this problem. This patch was tested against PostgreSQL. Same error with the connection. [junit] Running org.hibernate.test.ast.ASTIteratorTest [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,968 sec This test seems to be broken. [junit] Running org.hibernate.test.batchfetch.BatchFetchTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 81,937 sec Same error with the connection. [junit] Running org.hibernate.test.bidi.AuctionTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 8,203 sec Same error with the connection. [junit] Running org.hibernate.test.cid.CompositeIdTest [junit] Tests run: 4, Failures: 0, Errors: 4, Time elapsed: 51,828 sec Same error with the connection * 4. [junit] Running org.hibernate.test.collection.CollectionTest [junit] Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 122,875 sec Same error with the connection. + SQL Server uses brackets to "quote" identifiers. I created https://forge.continuent.org/jira/browse/SEQUOIA-908 and a patch to fix the problem (untested). Can you apply the patch, compile Sequoia, replace the controller jar in your Sequoia home directory and check that it solves this problem? [junit] Running org.hibernate.test.collection.bag.PersistentBagTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 6,39 sec java.lang.OutOfMemoryError: PermGen space. It doesn't seem to be a Sequoia error but a Hibernate one. [junit] Running org.hibernate.test.collection.idbag.PersistentIdBagTest Do you have the report for this one? It's not in your text file and the text report is empty. -- Guillaume _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
