Balaji, I would think that the changes discussed here are complementary. If we were to address this by moving 2.2 work to 2.1.X, it would be done in the 2.1.3-POST branch. Would you consider using the 2.1.3-POST branch in its entirety?
Also, posting errors you received, both the original CME and bean init errors, might be helpul to us. Randy --- [email protected] wrote: From: Balaji Chockalingam <[email protected]> To: [email protected] Subject: Jira Ticket JS2-761- Portal Fail To Come Up Date: Tue, 2 Jun 2009 08:43:03 -0700 (PDT) Hi, Recently I received ‘Concurrent Modification exception’ when I tried to export psml pages from portal database to file system. I found a similar issue addressed in JIRA ticket https://issues.apache.org/jira/browse/JS2-761. But this fix is applied only to the trunk and I believe it will be available in the latest release 2.2. I'm using Jetspeed portal version 2.1.3 along with the fix from database page manager cache where it’s been refactored to use ehcache from 2.1.3-POSTRELEASE. To resolve the issue of concurrent modification exception, I downloaded the files listed in JIRA ticket JS2-761, and merged it with the version we have. After merge, I try to bring up tomcat, found that the changes made to fix concurrent modification exception issue are not backward compatible, and so the portal fails to come up, since several beans fail to initialize. Please let me know if changes listed in JIRA ticket JS2-761 can work with the version I use(2.1.3 + fix from database page manager cache refactored to use ehcache from 2.1.3 POSTRELEASE) Thanks & Regards Balaji
