JBoss java.lang.OutOfMemoryError: PermGen space

This topic contains 12 replies, has 4 voices, and was last updated by  support-shalini 9 years, 9 months ago.

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #299889 Reply

    javaboy88
    Member

    *** Date:
    Friday, June 26, 2009 7:49:01 AM CDT

    ** System properties:
    OS=WindowsXP
    OS version=5.1.0
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 7.1.1
    Build id: 7.1.1-20090310

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 7.1.1
    Build id: 7.1.1-20090310

    Eclipse Platform

    Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
    Build id: M20080911-1700

    Eclipse Java Development Tools

    Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
    Build id: M20080709-0800

    Eclipse Graphical Editing Framework GEF

    Version: 3.4.1.v20080806-67718083A56B4H2A3213573
    Build id: 200809101400

    Eclipse RCP

    Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
    Build id: M20080703-0800

    Eclipse Plug-in Development Environment

    Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
    Build id: M20080703-0800

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\Program Files\Genuitec\MyEclipse 7.0\myeclipse.exe
    -name
    Myeclipse
    –launcher.library
    C:\Program Files\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
    -startup
    C:\Program Files\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
    -clean
    -configuration
    C:\Program Files\Genuitec\MyEclipse 7.0\configuration
    -vm
    C:\Program Files\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll

    I have googled this topic, searched this forum, and read everything I can find about it; but no solution so far. I have tried increasing MaxPermSize (to 512M most recently), but I’m still experiencing this problem. My application server is JBoss 4.2.2.GA and my JDK is 1.5.0_15. Any help will be greatly appreciated

    #299918 Reply

    javaboy88,
    Can you try placing the following
    -Xms128m -Xmx512m -XX:MaxPermSize=256m
    under Windows > Preferences > MyEclipse Enterprise Workbench > Servers > JBoss4.x > JDK > Optional Java VM Arguments.
    You can also increase “MaxPermSixe” in the above.

    #299923 Reply

    javaboy88
    Member

    These are the values I already had in those parameters:
    “-Xms256m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m”
    On one forum, one comment said that 512M usually cured this problem, but it didn’t help me much.

    #299924 Reply

    Ton Huisman
    Member

    Past experience has learned me to avoid the 1.5.0_15 release of Java (both JRE and JDK). Upgrading to 1.5.0_17 (or later) or downgrading to 1.5.0_11 could possibly dismiss this issue.

    HTH
    Ton

    #300310 Reply

    Loyal Water
    Member

    javaboy88,
    Did yo try upgrading to JDK 1.5.0_17 or later and test this again as suggest above? Did that help you resolve the issue?

    #300322 Reply

    javaboy88
    Member

    Upgraded to 1.5.0_19, but got the same result. jb88

    #300390 Reply

    Loyal Water
    Member

    Is this a popup dialog from MyEclipse/Eclipse that is showing the permgen space error OR is it in the server console?

    #300556 Reply

    javaboy88
    Member

    Neither. The error message appears on an application screen, copied directly from the JBoss server.log. Don’t know if any of this is related, but I found other exception and error messages in the log as follows: java.sql.SQLException: Table already exists: JMS_MESSAGES in statement [CREATE CACHED TABLE JMS_MESSAGES], java.sql.SQLException: Table already exists: JMS_TRANSACTIONS in statement [CREATE CACHED TABLE JMS_TRANSACTIONS], ERROR [STDERR] Jun 24, 2009 2:59:01 PM org.apache.cxf.endpoint.ServerImpl initDestination INFO: Setting the server’s publish address to be /TrustService (7 messages similar to this one), ERROR org.apache.myfaces.shared_tomahawk.config.MyfacesConfig – Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations (twice), ERROR [STDERR] Jun 24, 2009 3:12:36 PM org.apache.cxf.transport.https.SSLUtils getCiphersuites
    INFO: The cipher suites have not been configured, falling back to cipher suite filters (twice) – followed by: INFO: The cipher suites have been set to SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA, TLS_KRB5_WITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_RC4_40_SHA, TLS_KRB5_EXPORT_WITH_RC4_40_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA, TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5.

    #300572 Reply

    javaboy88,
    Those errors in the server log can be ignored. Please refer to the following link
    https://jira.jboss.org/jira/browse/JBAS-2389

    The error message appears on an application screen

    Can you send a screen shot of the error?

    #301189 Reply

    javaboy88
    Member

    Excuse the passage of time, but I have been “side-tracked” onto other and more urgent work for awhile.
    The behavior of the app has changed – it just displays a generic HTTP 500 message about not being able to display the page.
    Is there something else I can attach that might help to diagnose this problem?
    javaboy88

    #301203 Reply

    javaboy88,
    HTTP 500 error is generated when something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. Can you give some more information on this?
    1. Are there any error messages in the console?
    2. what is the application that you are trying to run?
    3. Can you paste the contents of the server log after you have run the application?

    #301305 Reply

    javaboy88
    Member

    Yes, console displays a message during server startup that port 1098 is already in use. it also displays the ” java.lang.OutOfMemoryError: PermGen space” message – same as what appears in the server log.
    The app is a proprietary system written for my employer.
    The server log is 821 KB. Are you sure I should “paste” all of that into this forum or is there some way to “attach” a file.
    Thanks, jb88

    #301348 Reply

    javaboy88,

    port 1098 is already in use

    Please refer to the following link for the above error
    http://www.jboss.org/?module=bb&op=viewtopic&t=67937
    You can paste relevant error messages from the log file. If the file is too long, you can send a a mail to support@genuitec.com. Please add ATTN: Shalini in the subject and refer to this thread or you can use the “pm” button at the end of the post.
    I would recommend you to cross post to Jboss forums also.

Viewing 13 posts - 1 through 13 (of 13 total)
Reply To: JBoss java.lang.OutOfMemoryError: PermGen space

You must be logged in to post in the forum log in