How many VelocityEngine's are you using? If one, then they should all be using the same IntrospectionCache, which has nothing to do with parsing and only relates to merging insofar as it is what is used to do reflection on the context objects used during merge. It's an eager cacher, so it automatically caches all public-in-public methods for the class of every context object used during the merging. But it only caches them once. This works great normally, but i've always suspected that if you were generating java classes on the fly and using them in templates, this could get out of hand. It's my suspicion that this is your problem.
On Mon, Oct 4, 2010 at 9:24 AM, Jason Tesser <[email protected]> wrote: > could this be from many parses or merges? We do have a bunch happening. > > Thanks, > Jason Tesser > dotCMS Lead Development Manager > 1-305-858-1422 > > > > On Mon, Oct 4, 2010 at 12:13 PM, Nathan Bubna <[email protected]> wrote: >> classes or something like that... >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
