Hi Geert, Done. :)
Josh -- Joshua Hansen Up Bear Enterprises (541) 760-7685 Geert Bevin wrote: > Hi Joshua, > > please file a Jira about this, so that it can at least be tracked and > so that I can at least find these links back easily. It will also be a > while before I can sink my teeth in this though. > > Take care, > > Geert > > On 18 Jul 2007, at 22:49, Joshua Hansen wrote: > >> Hi Geert, >> >> I should back up a second and apologize for sloppiness here -- I >> haven't actually profiled this or checked it, which should be done >> first. Some of the reading I did on the PermGen space issue >> initially indicated that this could be a problem, but some of what >> I'm finding now indicates that it might be ok if the class is >> constructed in a specific manner. >> >> http://blogs.sun.com/fkieviet/entry/classloader_leaks_the_dreaded_java >> http://blogs.sun.com/fkieviet/entry/how_to_fix_the_dreaded >> http://www.jroller.com/agileanswers/entry/preventing_java_s_java_lang#comments >> http://xlml.com/aehso/2007/04/05/the-dreaded-javalangoutofmemoryerror-permgen-space-exception/ >> >> But, as they say "Don't speculate -- profile." >> >> I'm happy to file a Jira request if you like, which I could do >> quickly. However, at this point I'm leaning toward writing a test >> case to confirm the problem. And it could be a little while before >> I get to it. >> >> Josh >> -- >> Joshua Hansen >> Up Bear Enterprises >> (541) 760-7685 >> >> >> >> Geert Bevin wrote: >>> Hi Joshua, >>> I think that this might be a limitation of the JVM. :-( >>> You can increase the tempgen space, but that's just postponing the >>> problem. A solution might be to create a new type of templates that >>> doesn't compile to byte-code, but that is purely in memory. It >>> shouldn't be actually that hard, I'll see if I can find the time >>> for this over the coming weeks. >>> Take care, >>> Geert >>> On 18 Jul 2007, at 00:54, Joshua Hansen wrote: >>>> Hi Geert and everyone, >>>> >>>> I wrote a CMS type system a little while back that allows users to >>>> enter template code as part of being able to edit a "live" page. >>>> The "content" was XML and was stored in the database, and I wrote >>>> ResourceFinders for reading and having the templates compiled. >>>> This is really cool because I can use elements with embedded >>>> properties as components that are included or configured as part >>>> of editing the normal HTML. >>>> >>>> The problem I've run into is that the VM (or Tomcat's container) >>>> doesn't seem to be throwing away expired template classes -- the >>>> expired classes end up in the permanent heap space (PermGen?). >>>> This means that as edits are made to pages and the templates are >>>> recompiled, memory gets consumed over time. >>>> >>>> Is anyone else doing this sort of thing? Has anyone else run into >>>> this? Suggestions? >>>> >>>> Josh >>>> --Joshua Hansen >>>> Up Bear Enterprises >>>> (541) 760-7685 >>>> >>> -- >>> Geert Bevin >>> Terracotta - http://www.terracotta.org >>> Uwyn "Use what you need" - http://uwyn.com >>> RIFE Java application framework - http://rifers.org >>> Music and words - http://gbevin.com > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
