Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7290

OutOfMemory error while using JBoss AS 5.1.0 with JBoss Native service on Windows

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: JBossAS-5.1.0.GA, 6.0.0.M1
    • Fix Version/s: No Release
    • Component/s: Other
    • Labels:
      None
    • Environment:
      Windows Operating System, JBoss Native
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      The setting of JAVA_OPTS=-Xrs can be removed from the service.bat and instead be placed in the run.bat.conf. See forum thread for more details.

      Show
      The setting of JAVA_OPTS=-Xrs can be removed from the service.bat and instead be placed in the run.bat.conf. See forum thread for more details.

      Description

      A couple of users have reported in the forums that AS 5.1.0 when used with the JBoss Native that is shipped with AS causes OutOfMemory errors on Windows. Here are the forum threads:

      http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161121
      http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161622

      The real issue is that the default JAVA_OPTS (in run.bat.conf) which set the -Xms, -Xmx and other memory settings are being skipped because the run.bat.conf does not set the JAVA_OPTS if its already set. The service.bat (from JBoss Native) sets the JAVA_OPTS (with -Xrs) which causes the run.conf.bat to just skip the part where other JAVA_OPTS are being set.

      The issue is being tracked in JBoss Native JBNATIVE-59 but i am opening this JBAS JIRA so that it gets tracked as part of the AS project too.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            jason.greene Jason Greene added a comment -

            Now that work is well underway with AS7, all previous community releases are end-of-lifed. So, all issues not directly assigned to an AS7 release are being closed.

            JBoss EAP is our supported enterprise version of AS, and you can file your issues against any release during its very long support window via CSP/RHN.

            If you believe your issue is still relevant to AS7 then please verify it and reopen.

            Show
            jason.greene Jason Greene added a comment - Now that work is well underway with AS7, all previous community releases are end-of-lifed. So, all issues not directly assigned to an AS7 release are being closed. JBoss EAP is our supported enterprise version of AS, and you can file your issues against any release during its very long support window via CSP/RHN. If you believe your issue is still relevant to AS7 then please verify it and reopen.

              People

              • Assignee:
                Unassigned
                Reporter:
                jaikiran jaikiran pai
              • Votes:
                1 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development