Page History

...

In a number of situations it is recommended or required to set Java options to specify the behavior of the JVM.

• Recommendations: JS7 - FAQ - Which Java Options are recommended?
• Troubleshooting: JS7 - Troubleshooting - Connection reset or Timeout reached (30s) for process and other articles.

Java options are set individually for the respective JS7 components, the Controller, Agent and JOC Cockpit.

...

• From the Unix command line or from the Controller instance start the controller_<instance>.sh script:

  Code Block
  language bash title Unix example to run the Controller start script with Java options
  # Set Java options before running the Controller start script export JAVA_OPTIONS="-Xms128m -Xmx500m" ./controller.sh start # Alternatively set Java options when running the Controller start script ./controller.sh start --java-options="-Xms128m -Xmx500m" # For use with a Controller daemon add this line to the Controller instance start script controller_<instance>.sh export JAVA_OPTIONS="-Xms128m -Xmx500m"

• From the Unix command line or from the Agent instance agent_4445.sh start script (assuming that port 4445 is used for the Agent):

  Code Block
  language bash title Unix example to run the Agent start script with Java options
  # Set Java options before running the Agent start script export JAVA_OPTIONS="-Xms128m -Xmx500m" ./agent.sh start # Alternatively set Java options when running the Agent start script ./agent.sh start --java-options="-Xms128m -Xmx500m" # For use with an Agent daemon add this line to the Agent instance start script agent_<port>.sh export JAVA_OPTIONS="-Xms128m -Xmx500m"

• Alternatively the JAVA_OPTIONS environment variable can be set with:
  • the profile (~/.bashrc, ~/.bash_profile etc.) of the run-time account used for Controller or Agent,
  • the JS7 - systemd Service Files for automated Startup / and Shutdown with Unix Systems.

Windows Operating Systems

...

• The Jetty start script is available from the installation directory  /opt/sos-berlin.com/js7/joc/jetty/bin/jetty.sh or  or a location specified during installation:

  Code Block
  language bash title Unix example to run the Jetty start script with Java options
  # Set Java options before running the Jetty start script export JAVA_OPTIONS="-Xms128m -Xmx500m" ./jetty.sh start

• When running the JOC Cockpit as a daemon then the following line can be added to the $HOME/.jocrc file of the JOC Cockpit run-time account. This file is created by the installer and it is used if it exists and is executable. The $HOME directory is identified from the /etc/passwd file during installation.

  Code Block
  language bash title Unix example to use $HOME/.jocrc with Java options
  export JAVA_OPTIONS="-Xms128m -Xmx500m"

  When running the JOC Cockpit as a daemon then the  /etc/default/joc file can be created (requires root permission) by the user. This file is not created by the installer and it will be used if it exists and is executable. This file will not be used if the 

  $HOME/.jocrc

   file is present as described above.

  Code Block
  language bash title Unix example to use /etc/default/joc with Java options
  export JAVA_OPTIONS="-Xms128m -Xmx500m"

• Alternatively the JAVA_OPTIONS environment variable can be set with:
  • the profile (~/.bashrc, ~/.bash_profile etc.) of the run-time account used for JOC Cockpit,
  • the JS7 - systemd Service Files for automated Startup / and Shutdown with Unix Systems.

Windows Operating Systems

...