Announcement Announcement Module
Collapse
No announcement yet.
java.lang.OutOfMemoryError: PermGen space Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • java.lang.OutOfMemoryError: PermGen space

    <Feb 26, 2013 2:47:13 PM MET> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListe ner failed: java.lang.OutOfMemoryError: PermGen space.
    java.lang.OutOfMemoryError: PermGen space

    after auto-deploying the war in weblogic 10.3 server. Any thought why this happened? Very simple application...
    Can I investigate the reason why this happened?


    This is how the server is configured
    JAVA_MEMORY : -Xms512m -Xmx512m -XX:PermSize=192m -XX:MaxPermSize=192m -XX:+UseParallelGC -XX:ParallelGCThreads=4 -XX:+UseParallelOldGC -XX:LargePageSizeInBytes=4m -XX:-BindGCTaskThreadsToCPUs

    similar topic:
    http://forum.springsource.org/showth...rmGen-space%29

    Is there any way to prevent this?
    Last edited by boom123; Feb 26th, 2013, 08:10 AM.

  • #2
    Don't auto-deploy... There are several frameworks/solutions which are notorious for memory leaks/classloader locking (commons-logging and cglib being 2 of them).

    Comment


    • #3
      Originally posted by Marten Deinum View Post
      Don't auto-deploy... There are several frameworks/solutions which are notorious for memory leaks/classloader locking (commons-logging and cglib being 2 of them).
      Attachment

      class:org.apache.log4j.config.PropertySetter[2 classes] instance count: 216.000 size 80.XXXkB


      I run Jprofiler to investigate the reason of this perm gen leak. I am new though to profiling apps, so can somebody give hos lights...
      Are all these instances of log4j needed? and why all this memory consumption?

      Thanks for your answers
      Attached Files
      Last edited by boom123; Mar 3rd, 2013, 11:04 AM.

      Comment


      • #4
        Originally posted by Marten Deinum View Post
        Don't auto-deploy... There are several frameworks/solutions which are notorious for memory leaks/classloader locking (commons-logging and cglib being 2 of them).

        If the application stops and the starts again? Should there be a problem with that or all the static classes are being removed from the classloader and this occurs only on auto-deploy?

        Comment


        • #5
          The behavior you see only occurs at auto-deploy/hot-deploy. Stopping, deploying, starting should not lead to these issues.

          Comment

          Working...
          X