Depending on which CipherSpec you use for SSL connection to your MQ Queue Manager from the MQMonitor agent, you may observe the following errors in the MQMonitor log:
Ciphers we have seen generating this error include:
cipherspec is specified in MQMonitor.properties:
# <Queue Manager>@<Host>.channel.ssl.cipherspec
# SSL cipherspec of the given Queue Manager to be monitored
# Default=none, if it is not set
QM1@hostname.channel.ssl.cipherspec = XXXXX_XXXXX
This problem is governed by the type of JVM used.
We recommend using the latest IBM JVM to run the MQMonitor, as it provides support for CipherSpecs that may be unavailable with an Oracle JVM.
It was noted that TRIPLE_DES_SHA_US works with both IBM and Oracle JVMs.