Using JRE diagnostic options

In some cases you might need to use diagnostic functions that are built into the Java runtime environment (JRE). You should usually do this only under the direction of an IBM® Support representative, as some diagnostic settings might impair normal MQIPT operation.

The MQIPT_JVM_OPTIONS environment variable can be used to pass diagnostic options to the underlying MQIPT JRE by using the command line. All command parameters that are valid for the IBM JRE supplied with MQIPT can be used.

You can use the common diagnostic option -Djavax.net.debug=all to enable diagnostics for SSL/TLS and network throughput. Setting this option causes a detailed log of internal network operations to be written to the console where MQIPT was started. This is useful for debugging SSL/TLS handshake errors on routes with SSLClient or SSLServer set to true.

Here is an example of enabling this setting on AIX® and Linux® platforms:

MQIPT_JVM_OPTIONS="-Djavax.net.debug=all"  
export MQIPT_JVM_OPTIONS

Here is an example of enabling this setting on Windows platforms:

set MQIPT_JVM_OPTIONS=-Djavax.net.debug=all

For this setting to take effect, you must restart MQIPT from the command prompt where the environment variable is set.