Menu ▾ ▴

353: Jboss MaxPermGen java options problem

Developers
Bayu Cahya P
2009-04-25
2013-03-08

  • Bayu Cahya P

    Bayu Cahya P - 2009-04-25

    Hi,

    Yesterday, I have tried to clean and build completely new ADempiere 353.
    After running setup, everything goes fine.

    The problem is, we can not start to running jboss application server (run_server2.bat).
    Checking internally, the problem was in this jboss\bin\run.conf file in line 43

    JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermGen=128m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"

    and in the jboss\bin\run.bat file in line 73

    set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermGen=128m

    This is show stopper issues.

    As per http://blogs.sun.com/watt/resource/jvm-options-list.html, the valid option is -XX:MaxPermSize=128m instead of -XX:MaxPermGen=128m.

    Altering this java options should fixing this issues.

    regards
    Bayu Cahya P
    http://sistematika.web.id

     

    • Michael Judd

      Michael Judd - 2009-04-27

      Hi,

      I saw your fix on this: rev 9100

      This bug appeared to be introduced in BF [2779124] OutOfMemoryError: PermGen space *set -XX:MaxPermGen=128m

      I might be helpful to have a bug logged on this and then to reference this discussion for completeness or to update the BF referenced above.  I think the practise is to reference the bug tracker in the commit.

      Either way - a step forward,

      Thanks

      Mike

       

    • Mario Calderon

      Mario Calderon - 2009-04-27

      Hi,

      is there any side effects changing these parms?

      I do not know JBoss, but there are many things involved: java version, operating system, revision etc. which should be accounted for. Has they all been checked before committing?

      Best regards,
      Mario Calderon

       

Log in to post a comment.