[V9.0.0.10 May 2020]

What's changed in IBM MQ 9.0.0 Fix Pack 10

IBM® MQ 9.0.0 Fix Pack 10 includes two resource changes.

Change to default trace name for IBM MQ classes for Java and IBM MQ classes for JMS

From IBM MQ 9.0.0 Fix Pack 10, the IBM MQ classes for Java, IBM MQ classes for JMS and IBM MQ resource adapter have been updated such that when threads are running using separate Java ClassLoaders, by default, each thread generates trace to its own ClassLoader specific trace file:
  • The default trace name for the IBM MQ classes for Java and IBM MQ classes for JMS is of the form: mqjava_%PID%.cl%u.trc.
  • If you are using the relocatable JAR file com.ibm.mq.mqallclient.jar, the default trace name is of the form: mqjavaclient_%PID%.cl%u.trc.
where %PID% is the process identifier of the application that is being traced, and %u is a unique number to differentiate files between threads running trace under different Java classloaders.

For more information, see the subtopics of Tracing IBM MQ classes for Java applications and Tracing IBM MQ classes for JMS applications.

[UNIX, Linux, Windows]

Update to IBM MQ AMQP service

From IBM MQ 9.0.0 Fix Pack 10, the IBM MQ AMQP service has been updated such that when the SSLPEER attribute is set and the SSLCAUTH attribute is set to REQUIRED, the "distinguished name" of the client certificate is checked with the SSLPEER attribute.

For more information, see Creating and using AMQP channels.