Page History
...
Output created from Java debug options is written to the stdout channel and therefore is added to the watchdog.log
file in the Controller's or Agent's logs
directory, see JS7 - Log Files and Locations.
...
Unix Operating Systems
For WindowsUnix, the JAVA_OPTIONS
environment variable can be set before running the Controller or Agent start script like this:
from From the Windows Unix command line or from the Controller instance start script
controller_<instance>.cmdsh
:Code Block language bash title Windows Unix example to run the Controller start script with debug options @rem# Set debug options before running the Controller start script setexport JAVA_OPTIONS="-Djavax.net.debug=ssl" .\/controller.cmdsh start @rem# Alternatively set debug options when running the Controller start script .\/controller.cmdsh start --java-options="-Djavax.net.debug=ssl" @rem# For use with a Controller Windows servicedaemon add this line to the Controller instance start script controller_<instance>.cmdsh setexport JAVA_OPTIONS="-Djavax.net.debug=ssl"
from From the Windows Unix command line or from the Agent instance start script
agent_4445.cmdsh
(assuming that port4445
is used for the Agent):Code Block language bash title Windows Unix example to run the Agent instance start script with debug options @rem# Set debug options before running the Agent start script from the command line set JAVA_OPTIONS export JAVA_OPTIONS="-Djavax.net.debug=ssl" .\/agent.cmdsh start @rem# Alternatively set debug options when running the Agent start script .\/agent.cmdsh start --java-options="-Djavax.net.debug=ssl" @rem# For use with an Agent Windows servicedaemon add this line to the Agent instance start script agent_<port>.cmdsh setexport JAVA_OPTIONS="-Djavax.net.debug=ssl"
- Alternatively , when operating the Controller or Agent as a Windows Service then from the .
\service
directory of the installation run - for a Controller:
js7_controller_<controller-id>w.exe
- where
<controller-id>
corresponds to the Controller ID the Controller has been installed for. - Example:
C:\Program Files\sos-berlin.com\js7\controller\my-controller\service\js7_controller_mycontrollerw.exe
- where
- for an Agent:
js7_agent_<port>w.exe
- where
<port>
corresponds to the port that the Agent is operated for. - Example:
C:\Program Files\sos-berlin.com\js7\agent_4445\service\js7_agent_4445w.exe
This brings up a utility that allows Java options to be specified: - where
- Note that the Controller or Agent 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 Controller or Agent start script like this:
- the
JAVA_OPTIONS
environment variable can be set with the JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems.
Windows Operating Systems
For Windows, the JAVA_OPTIONS
environment variable can be set before running the Controller or Agent start script like this:
From the Windows command line or from the Controller instance start script
controller_<instance>.cmd
: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
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 @rem For use with a Controller Windows Service add this line to the Controller instance start script ./ controller_<instance>.sh start --java-optionscmd set JAVA_OPTIONS="-Djavax.net.debug=ssl" # For use with a Controller daemon add this line to the Controller instance start script controller_<instance>.sh export JAVA_OPTIONS="-Djavax.net.debug=ssl"
From the Windows command line or from the Agent instance start script
agent_4445.cmd
(assuming that port4445
is used for the Agent):Code Block language bash title Unix Windows example to run the Agent instance start script with debug options #@rem Set debug options before running the Agent start script export frm the command line set JAVA_OPTIONS="-Djavax.net.debug=ssl" ./\agent.shcmd start #@rem Alternatively set debug options when running the Agent start script ./\agent.shcmd start --java-options="-Djavax.net.debug=ssl" #@rem For use with an Agent Windows daemonService add this line to the Agent instance start script agent_<port>.shcmd exportset JAVA_OPTIONS="-Djavax.net.debug=ssl"
- Alternatively the
JAVA_OPTIONS
environment variable can be set with the JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems.
Applying Debug Options to JOC Cockpit
Log File
Output created from Java debug options is written to the stdout channel and therefore is added to the jetty.log
file in the JOC Cockpit's logs
directory, see JS7 - Log Files and Locations.
Windows Operating Systems
For Windows, the JAVA_OPTIONS
environment variable can be set before running the JOC Cockpit start script like this:
- , when operating the Controller or Agent as a Windows Service then from the .
\service
directory of the installation run- for a Controller:
js7_controller_<controller-id>w.exe
- where
<controller-id>
corresponds to the Controller ID the Controller has been installed for. - Example:
C:\Program Files\sos-berlin.com\js7\controller\my-controller\service\js7_controller_mycontrollerw.exe
- where
- for an Agent:
js7_agent_<port>w.exe
- where
<port>
corresponds to the port that the Agent is operated for. - Example:
C:\Program Files\sos-berlin.com\js7\agent_4445\service\js7_agent_4445w.exe
- where
- This brings up a utility that allows Java options to be specified:
- Note: The Controller or Agent Windows Service has to be restarted to apply changes to Java options.
- for a Controller:
Applying Debug Options to JOC Cockpit
Log File
Output created from Java debug options is written to the stdout channel and therefore is added to the jetty.log
file in the JOC Cockpit's logs
directory, see JS7 - Log Files and Locations.
Unix Operating Systems
For Unix the JAVA_OPTIONS
environment variable can be set before running the Jetty start script like this:
The Jetty start script is available from the installation directory
/opt/sos-berlin.com/js7/joc/jetty/bin/jetty.sh
or a location specified during installation: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 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 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 debug options export
Only when JOC Cockpit is not installed as Windows Service then the start script
C:\Program Files\sos-berlin.com\js7\joc\jetty\bin\jetty.cmd
is available.
When operating the JOC Cockpit as a Windows Service then from the .Code Block language bash title Windows example to run the JOC Cockpit start script with debug options @rem Set debug options before running the JOC Cockpit start script set JAVA_OPTIONS="-Djavax.net.debug=ssl" .\jetty.cmd start
\service
directory of the installation run- for JOC Cockpit:
js7_jocw.exe
- Example:
C:\Program Files\sos-berlin.com\js7\joc\service\js7_jocw.exe
This brings up a utility that allows Java options to be specified: - Example:
- Note that the JOC Cockpit Windows Service has to be restarted to apply changes to Java options.
Unix Operating Systems
...
debug=ssl"
When running 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, it will be used if it exists and is executable. This file will not be used if the$HOME/.jocrc
file is present, see above.Code Block language bash title Unix example to run the Jetty start script with debug optionsuse /etc/default/joc with debug options # Set debug options before running the Jetty start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./jetty.sh startssl"
- Alternatively the
JAVA_OPTIONS
environment variable can be set with the JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems.
Windows Operating Systems
For Windows, the JAVA_OPTIONS
environment variable can be set before running the JOC Cockpit start script like this:
Only when JOC Cockpit is not installed as Windows Service then the start script
C:\Program Files\sos-berlin.com\js7\joc\jetty\bin\jetty.cmd
is availableWhen running 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 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 Windows example to use $HOME/.jocrc run the JOC Cockpit start script with debug options export@rem Set debug options before running the JOC Cockpit start script set JAVA_OPTIONS="-Djavax.net.debug=ssl" .\jetty.cmd start
- When running operating 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, it will be used if it exists and is executable. This file will not be used if the$HOME/.jocrc
file is present, see above.
Alternatively theCode Block language bash title Unix example to use /etc/default/joc with debug options export JAVA_OPTIONS="-Djavax.net.debug=ssl"
JAVA_OPTIONS
environment variable can be set with the JS7 - systemd Service Files for automated Startup / Shutdown with Unix SystemsWindows Service then from the .\service
directory of the installation run- for JOC Cockpit:
js7_jocw.exe
- Example:
C:\Program Files\sos-berlin.com\js7\joc\service\js7_jocw.exe
- Example:
- This brings up a utility that allows Java options to be specified:
- Note that the JOC Cockpit Windows Service has to be restarted to apply changes to Java options.
- for JOC Cockpit:
Frequently Used Debug Options
...