Skip to main content

MarkView Application Server - WildFly server: JAVA_OPTS not being applied

Article # 304162 - Page views: 579



Applies To

  • MarkView for Oracle (9.0 and later)
  • MarkView for SAP 9.0
  • WildFly application server


  • No MarkView application log files are generated even though the -Dmarkview.home option has been include in the JBOSS_HOME/bin/standalone.conf configuration file as described in the MarkView Installation Guide.
  • WildFly log (wildfly-stdout.<date>.log) shows value for JAVA_OPTS which does not match values specified in standalone.conf file. e.g.:
  2018-05-14 05:01:59 Commons Daemon procrun stdout initialized
      Calling "C:\MarkView\bin\standalone.conf.bat" Setting JAVA property to "C:\Program

          JBoss Bootstrap Environment
          JBOSS_HOME: "C:\MarkView"
          JAVA: "C:\Program Files\Java\jdk1.8.0_91\bin\java"

          JAVA_OPTS: " -Xms1024M -Xmx2048M -XX:MaxPermSize=256M - -Djboss.modules.system.pkgs=org.jboss.byteman"


Known Causes

  • The default code for assigning JAVA_OPTS in the standalone.conf file includes an if statement - e.g.
      # Specify options to pass to the Java VM.
      if [ "x$JAVA_OPTS" = "x" ]; then
         JAVA_OPTS="-Xms2g -Xmx2g -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=512m -"
         JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -
      Djava.awt.headless=true -Dmarkview.home=/projects/wl01/home/mvwl01/mv/"
         echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"

  • Therefore if JAVA_OPTS is set as an environment variable, the assignment of the -Dmarkview.home option will be bypassed.


  • Remove the if construct from the standalone.conf file and ensure that the assignment of JAVA_OPTS contains all necessary options.

Keywords: JAVA_OPTS, -Dmarkview.home, standalone.conf, JBOSS, -Xms, -Xmx, PermSize