[Cosmo-dev] QA Cosmo Performance after Migration

[Adam Christian]

Today I updated QA Cosmo to 0.8.0, and have since been trying to run  
automated tests against it which have been taking unbearably long to  
run. My testing this morning against 0.7.4 RC3 was speedy as normal.  
This is the first time I have ever used the migration scripts and in  
the logs see the following types of errors:

2007-10-09 17:50:31,467 ERROR [AbstractFlushingEventListener] Could  
not synchronize database state with session
org.hibernate.exception.ConstraintViolationException: could not  
delete: [org.osaf.cosmo.model.CollectionItem

Caused by:  
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException:  
Cannot delete or update a parent row: a foreign key constraint fails  
(`Cosmo/collection_item`, CONSTRAINT `FK3F30F8148B8DC8EF` FOREIGN KEY  
(`collectionid`) REFERENCES `item` (`id`))

2007-10-09 17:50:31,576 ERROR [StandardRequestHandler] Internal dav  
error

2007-10-09 17:54:23,758 ERROR [AbstractFlushingEventListener] Could  
not synchronize database state with session
2007-10-09 17:54:23,764 ERROR [StandardRequestHandler] Internal dav  
error
2007-10-09 17:54:36,327 ERROR [XmlClobType] Error deserializing XML clob
2007-10-09 17:54:36,470 ERROR [XmlClobType] Error deserializing XML clob

Mikeal and I are both seeing load times starting at 8 seconds up to 25 
+ for me simply pulling up the login page.

Could someone take a look at this?

If you log into QA Cosmo the log is in ~/latest-rc/logs/osafsrv.log

Adam