JMS: changes to IBM MQ classes for JMS
For IBM® MQ 8.0, a number of changes are made to IBM MQ classes for JMS.
Enforcement of unique client IDs
As required by the JMS 2.0 specification, the
IBM MQ classes for
JMS now check that non-null client ids that are
provided when making a connection are unique. If not, a
javax.jms.InvalidClientIDException
is thrown.
Some existing applications that relied on the previous behavior, and that reused client ids, might now fail. To allow such applications to continue to run without coding changes, the check for client id uniqueness can be disabled by setting the system property com.ibm.mq.jms.SupportMQExtensions
to true
when starting an application.
Changes to CipherSuite support
See Java and JMS: changes to CipherSuite support for further information.
Removal of support for Direct
and DirectHTTP
transport
Direct
and DirectHTTP
transport were deprecated in a previous release of IBM MQ and they have been removed at IBM MQ 8.0.
JMSFMQ1006: The value of 'DirectIP' for property 'Transport Type' is not valid.