Hi Sean, We also did the transition to JackRabbit 1.3.3 before Magnolia did. And we are facing to the same problem. I would enjoy to work with you to solve this issue or at least to find a hack or some workaround.
Regards, CAPITAINE Harold > Hi Folks, > > We upgraded to Jackrabbit 1.3.3 over the break, looking forward to the > performance and reliability enhancements it promised. Unfortunately, we > have > found that it uses a ton more memory than the older version of Jackrabbit > did. As a result, our public instance has become very unstable, as it > tends > to exhaust the available 1GB within about 75 minutes. Since we're using > BDB > as our data store, having to forcibly shut down tomcat also appears to be > introducing data corruption, as we've been having more and more nodes that > are unable to be updated or deleted in the public instance. This, of > course, > makes our users very unhappy indeed. > > Since the memory use appears to grow steadily, this seems very much like a > memory leak, and appears to be present both when using BDB or PostGreSQL > for > persistence, and under both Magnolia 3.0.5 and Magnolia 3.5. > > We're faced now with reverting to the earlier version of Jackrabbit and > tweaking the XML for all of our 200 sites so that it can be imported by > the > earlier version of Jackrabbit. > > Needless to say, we'd very much like to avoid this scenario. If any one > can > provide any help to get Jackrabbit 1.3.3's memory usage under control, > we'd > very much like to hear it. > > Thanks in advance for any insight. > > Sean > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
