Page History

...

Such options are applied for specific areas of interest and are forwarded by use of the JAVA_OPTIONS environment variable.

Applying debug options requires the JS7 component in question to be restarted.

...

The below examples make use of the -Djavax.net.debug=ssl Java option that is used to receive detailed information e.g. about SSL certificate handling. However, any Java options can be forwarded like this.

Log File

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.

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="-Djavax.net.debug=ssl" @rem For use with a Controller Windows service add this to the Controller instance start script controller_<instance>.cmd set JAVA_OPTIONS="-Djavax.net.debug=ssl"

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

  Code Block
  language bash title Windows 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="-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" @rem For use with an Agent Windows service add this to the Agent instance start script agent_<port>.cmd set JAVA_OPTIONS="-Djavax.net.debug=ssl"

• When Alternatively, 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
  • This brings up a utility that allows Java options to be specified:
    • 
  • Note that the Controller or Agent Windows Service has to be restarted to apply changes to Java options.

...

• When configuring certificates for secure HTTPS connections with JOC Cockpit, Controller and Agents then SSL debug options will provide detailed information e.g. about handshaking and use of certificates.
• Use the Java option: -Djavax.net.debug=ssl or -Djavax.net.debug=all
• Find debug output
  • of SSL certificate negotiation related to a Controller or Agent with the log file watchdog.log
  • of general authentication steps with the JOC Cockpit log file authentication-debug.log
  • of SSL connections with the JOC Cockpit log file jetty.log.

...