Use JRE diagnostic options

In some cases you might need to use diagnostic functions that are built into the Java runtime environment (JRE). We should usually only do this under the direction of the IBM Software 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 via the command line. All command parameters that are valid for the IBM JRE supplied with MQIPT can be used.

-Djavax.net.debug=all

This option enables 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 particularly useful for debugging SSL/TLS handshake errors on routes with SSLClient or SSLServer set to true.

-Djava.security.debug=access,failure

This option enables diagnostics for the Java Security Manager policy, for MQIPT instances with SecurityManager set to true. Setting this option causes a detailed log of security activities and their required permissions to be written to the console where MQIPT was started. It can be used to identify missing permissions in the policy file.

Here is an example of enabling both of these settings on Windows platforms:

set MQIPT_JVM_OPTIONS=-Djavax.net.debug=all -Djava.security.debug=access,failure

MQIPT_JVM_OPTIONS="-Djavax.net.debug=all -Djava.security.debug=access,failure"  
export MQIPT_JVM_OPTIONS

For these settings to take effect, we must restart MQIPT from the command prompt where the environment variable is set.

For another use of MQIPT_JVM_OPTIONS when diagnosing problems, see Tracing errors in mqiptKeyman and mqiptKeycmd.