[ http://jira.magnolia.info/browse/MAGNOLIA-1140?page=comments#action_13532 ] Fabrizio Giustina commented on MAGNOLIA-1140: ---------------------------------------------
I did several tests on a website running on magnolia 3.0.1, upgrading the jackrabbit dependency from 1.0.1 to 1.2.1: tested heavy copy operations on website trees with many pages/heavy binary properties, tested move, delete, activate... result: no problem at all for me :) by simply upgrading jackrabbit from 1.0.1 to 1.2.1 I got no errors at all. Sameer, could you post the errors you are getting? Maybe the culprit is not jackrabbit itself, check if the problem for you could be: - lucene upgraded to 2.0: you should be able to delete the lucene index and to see if this helps - derby version: the new version of jackrabbit uses a newer derby version: although I never had problems in upgrading derby you might want to try with the same version used by magnolia 3.0.1 In a few days jackrabbit 1.2.2 will be out, with the few interesting enhancements related to clustering: as soon as this upgrade issue is cleared I would like to vote a release for 3.1 (as previously said the jackrabbit upgrade really worths it). > move to jackrabbit 1.2.x > ------------------------ > > Key: MAGNOLIA-1140 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1140 > Project: Magnolia > Issue Type: Improvement > Reporter: Philipp Bracher > Assigned To: Fabrizio Giustina > Priority: Critical > Fix For: 3.1 > > Attachments: POM & PDM Issue Analysis Workbook.xls > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
