glassfish
  1. glassfish
  2. GLASSFISH-1855

Permgen leak : backport or fix confirm for 9.0.1

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 9.0peur1
    • Fix Version/s: 9.1pe
    • Component/s: other
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      1,855
    • Status Whiteboard:
      Hide

      as91-na,as91ur1-na

      Show
      as91-na,as91ur1-na

      Description

      I am currently running 9.0.1 build 14 with a JDK1.6.0 FCS with a 1GB allocated
      (put 1GB to make the problem happen less often). I got 1 EAR deployed and about
      5 WAR on it. After 3 days, of run, I got the permgen leak problem, (going on a
      stop-domain could even kill the box) so, only solution is to kill -9 the java
      process !

      As Issue 587 was reported on the 9.0 branch (the stable one), this issue is to
      make sure this branch (9.0.1 at this time) has fixed this major issue that still
      prevent GF to be used as a stable product in production environment.

      Issue 587 logs was not clear wether backport from 9.1 to 9.0.1 was done at this
      time.

      Sorry for posting this in a new issue, but the issue tracker still prevent me
      from posting comments directly inside 587 !?!

      Best Rgs,
      JB

        Issue Links

          Activity

          Hide
          bjb added a comment -

          Link with 587 as this is the issue, this is all about.

          Show
          bjb added a comment - Link with 587 as this is the issue, this is all about.
          Hide
          jluehe added a comment -

          Issue 587 lists the commits that fixed the memory leaks, and how they've been
          backported to 9.0peur1. For example, search for "Fix has been backported to
          9.0peur1, b02", or "Commit to 9.0peur1".

          Notice that the OutOfMemory problem in Issue 587 occurred after several
          redeployments. From your description, it is not clear if you are running out of
          memory after several redeployments, or during a "continuous" run. Can you please
          clarify? Thanks!

          Show
          jluehe added a comment - Issue 587 lists the commits that fixed the memory leaks, and how they've been backported to 9.0peur1. For example, search for "Fix has been backported to 9.0peur1, b02", or "Commit to 9.0peur1". Notice that the OutOfMemory problem in Issue 587 occurred after several redeployments. From your description, it is not clear if you are running out of memory after several redeployments, or during a "continuous" run. Can you please clarify? Thanks!
          Hide
          bjb added a comment -

          Created an attachment (id=672)
          GF 9.0.1b14 running on a JDK6.1FCS over Linux 2.6.9-27 with 1GB allocated to the VM got stuck at 100% CPU after less than 7 days with 1 EAR and 5 WAR running at low traffic

          Show
          bjb added a comment - Created an attachment (id=672) GF 9.0.1b14 running on a JDK6.1FCS over Linux 2.6.9-27 with 1GB allocated to the VM got stuck at 100% CPU after less than 7 days with 1 EAR and 5 WAR running at low traffic
          Hide
          Mahesh Kannan added a comment -

          Changing the sub category to other

          Show
          Mahesh Kannan added a comment - Changing the sub category to other
          Hide
          jluehe added a comment -

          Hi Jean-Baptiste,

          I'm downgrading this to a P3 for the time being. I sent you mail earlier this
          morning, asking you to increase your MaxPermSize to 256m, by adding this JVM
          property to your domain.xml:

          <jvm-options>-XX:MaxPermSize=256m</jvm-options>

          Let us know if this helps. If it doesn't, we'll look into possible leaks in the
          appserver or possibly your app(s).

          We've noticed that when deploying and running a bunch of tests on the SDK with
          JDK 1.6 installed (which is the JDK version you are using), we had to increase
          the MaxPermSize to 256m, when half that size had been sufficient with JDK 1.5.

          Show
          jluehe added a comment - Hi Jean-Baptiste, I'm downgrading this to a P3 for the time being. I sent you mail earlier this morning, asking you to increase your MaxPermSize to 256m, by adding this JVM property to your domain.xml: <jvm-options>-XX:MaxPermSize=256m</jvm-options> Let us know if this helps. If it doesn't, we'll look into possible leaks in the appserver or possibly your app(s). We've noticed that when deploying and running a bunch of tests on the SDK with JDK 1.6 installed (which is the JDK version you are using), we had to increase the MaxPermSize to 256m, when half that size had been sufficient with JDK 1.5.
          Hide
          Alexis MP added a comment -

          met bjb. problem still ongoing.

          Show
          Alexis MP added a comment - met bjb. problem still ongoing.
          Hide
          sridatta added a comment -

          adding as91-na flag since it is already fixed in AS9.1

          Show
          sridatta added a comment - adding as91-na flag since it is already fixed in AS9.1
          Hide
          jluehe added a comment -

          Have not encountered this in 9.1 UR1

          Show
          jluehe added a comment - Have not encountered this in 9.1 UR1
          Hide
          jluehe added a comment -

          Closing as WONTFIX, since there is no active development on 9.0peur1, and the
          issue seems to have been fixed in 9.1 and onward.

          Show
          jluehe added a comment - Closing as WONTFIX, since there is no active development on 9.0peur1, and the issue seems to have been fixed in 9.1 and onward.

            People

            • Assignee:
              jluehe
              Reporter:
              bjb
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: