Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5403

The jvm options in run.conf.bat get ignored when using service.bat

    XMLWordPrintable

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      set the JVM options one place only

      (in service.bat or run.conf.bat)

      Show
      set the JVM options one place only (in service.bat or run.conf.bat)
    • Release Notes Text:
      Hide
      When starting the server using service.bat, no options were inherited from run.conf.bat. This occurred because service.bat set JAVA_OPTS to a placeholder value, which was not overridden by values set in run.conf.bat due to a faulty check. This issue has been fixed, and options set in run.conf.bat are now used when starting the server with service.bat.
      Show
      When starting the server using service.bat, no options were inherited from run.conf.bat. This occurred because service.bat set JAVA_OPTS to a placeholder value, which was not overridden by values set in run.conf.bat due to a faulty check. This issue has been fixed, and options set in run.conf.bat are now used when starting the server with service.bat.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      If you use service.bat and have your jvm options set in run.conf.bat they will be ignored.

      This happens because service.bat sets %JAVA_OPTS% by

      set JAVA_OPTS=-Xrs

      later on, service.bat uses run.bat which calls run.bat.conf
      in run.bat.conf there is a check to see if %JAVA_OPTS% are set -

      if not "x%JAVA_OPTS%" == "x" goto JAVA_OPTS_SET

      so, if JAVA_OPTS are set it doesn't jump to :JAVA_OPTS_SET
      and the script carries on and sets all the vm parameters at

      rem # JVM memory allocation pool parameters - modify as appropriate.

      set "JAVA_OPTS=-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true"

      So when using service.bat these parameters get ignored.

      I note that this is mentioned in https://jira.jboss.org/browse/JBNATIVE-59 and the fix for service.bat overwriting %JAVA_OPTS% is in currently in trunk.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rsvoboda Rostislav Svoboda
                  Reporter:
                  ShaunA Shaun Appleton
                  Writer:
                  Elspeth Thorne
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Due:
                    Created:
                    Updated:
                    Resolved: