Hotfixes
A hotfix update is a single minor release to address a problem in a Deephaven release. Typically, hotfixes are made to address a specific customer situation.
If a hotfix is applicable to your current Deephaven deployment, your Deephaven account representative will provide you with the hotfix installation package.
Copy the new packages onto your Deephaven Linux hosts and run the following commands to apply the hotfix:
sudo yum localinstall illumon-db-<VERSION>.rpm -y
The installation procedure for a hotfix is similar to regular Deephaven upgrades. The installer will not delete or overwrite any existing files. It simply lays down the new files and updates a symbolic link called latest in the /usr/illumon folder.
The Reference section of the Deephaven Documentation includes the full version log for active Deephaven versions.
Custom Libraries, Overrides and Hotfixes
Any custom or third party libraries and resources, such as JARs, class files, property files, etc. can be added to designated directories to override and/or extend your Deephaven installation.
The following directories are placed in the front of the CLASSPATH of Deephaven processes. Add any custom or third party resources to the following directories:
/etc/sysconfig/illumon.d/java_lib- For any user and/or third-party Java libraries (JARs). Any JARs placed in this directory will be found on the classpath of Deephaven processes./etc/sysconfig/illumon.d/override- For class files or other Java resources that should override those contained in thejava_libJARs./etc/sysconfig/illumon.d/hotfixes- This path contains any JAR files that should be used instead of those contained in thejava_libdirectories.
Restart affected processes
After a Deephaven hotfix package has been applied or any custom libraries, overrides or custom hotfixes have been placed in designated directories, the affected Deephaven processes need to be restarted.
In most cases, a restart of all Deephaven processes on the server will be required. This is accomplished using the following command:
sudo monit restart all
In cases where the hotfix or custom extensions are applicable to a specific Deephaven process, only that process needs to be restarted. Please refer to the Startup/Shutdown of Deephaven Processes section for instructions on restarting individual Deephaven processes.
Troubleshooting custom hotfixes and extensions
In some cases, third party libraries, custom extensions or hotfixes can cause conflicts or errors with existing Deephaven code libraries. Refer to the Log files for any errors or warnings once processes have been restarted with custom extensions.
Debugging process configuration
Use the sudo jinfo <pid> command to print Java configuration information for a specified Java process like the CLASSPATH and other useful info about a running Java process.
Debugging SSL/TLS Connections
Understanding SSL/TLS connection problems can sometimes be difficult, especially when it is not clear what messages are actually being sent and received.
You can get excellent certificate debugging by adding -Djavax.net.debug=all to your Java launch parameters to help troubleshoot or diagnose SSL/TLS Connections.