Page History
...
Debug Options for Controller and Agent
Windows Operating Systems
For Windows the JAVA_OPTIONS environment variable can be set before running the Controller or Agent start script like this:
Code Block language bash title Windows example to run the Controller start script with debug options @rem Set debug options before running the Controller start script set JAVA_OPTIONS="-Djavax.net.debug=ssl" .\controller.cmd start @rem Alternatively set debug options when running the Controller start script .\controller.cmd start --java-options="-Djavax.net.debug=ssl"
Code Block language bash title Windows example to run the Agent start script with debug options @rem Set debug options before running the Agent start script set JAVA_OPTIONS="-Djavax.net.debug=ssl" .\agent.cmd start @rem Alternatively set debug options when running the Agent start script .\agent.cmd start --java-options="-Djavax.net.debug=ssl"
- When operating the Controller or Agent as a Windows Service then from the .
\service
directory of the installation run- for a Controller:
sos_jobscheduler_controller_<port>w.exe
- for an Agent:
sos_jobscheduler_agent_<port>w.exe
- where
<port>
corresponds to the port that the Controller or Agent has been installed for. - Example:
C:\Program Files\sos-berlin.com\js7\agent_4445\service\sos_jobscheduler_agent_4445w.exe
- where
- This brings up a utility that allows to specify Java options:
- Consider that the Controller or Agent Windows Service has to be restarted to apply changes to Java options.
- for a Controller:
Unix Operating Systems
For Unix the JAVA_OPTIONS environment variable can be set before running the Controller or Agent start script like this:
Code Block language bash title Unix example to run the Controller start script with debug options # Set debug options before running the Controller start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./controller.sh start # Alternatively set debug options when running the Controller start script ./controller.sh start --java-options="-Djavax.net.debug=ssl"
xxxCode Block language bash title Unix example to run the Agent start script with debug options # Set debug options before running the Agent start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./agent.sh start # Alternatively set debug options when running the Agent start script ./agent.sh start --java-options="-Djavax.net.debug=ssl"
Debug Options for JOC Cockpit
Windows Operating Systems
For Windows the JAVA_OPTIONS environment variable can be set before running the JOC Cockpit start script like this:
Code Block language bash title Windows example to run the Controller start script with debug options @rem Set debug options before running the Controller start script set JAVA_OPTIONS="-Djavax.net.debug=ssl" .\jetty.cmd start
- When operating the JOC Cockpit as a Windows Service then from the .
\service
directory of the installation run- for JOC Cockpit:
sos_joc_<port>w.exe
- where
<port>
corresponds to the port that the JOC Cockpit
- where
- for JOC Cockpit:
...
- has been installed for.
- Example:
C:\Program Files\sos-berlin.com\js7\joc\service\sos_joc_4446w.exe
- This brings up a utility that allows to specify Java options:
- Consider that the JOC Cockpit Windows Service has to be restarted to apply changes to Java options.
Unix Operating Systems
For Unix the JAVA_OPTIONS environment variable can be set before running the Jetty start script like this:
Code Block language bash title Unix example to run the Jetty start script with debug options # Set debug options before running the Jetty start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./jetty.sh start
When running JOC Cockpit as a daemon the following line can be added to the
/etc/default/joc
file (requires root permissions):Code Block language bash title Unix example to use /etc/default/joc with debug options export JAVA_OPTIONS="-Djavax.net.debug=ssl"