Limitations of the IBM MQ resource adapter

The IBM® MQ resource adapter is supported on all IBM MQ platforms. However, when you use the IBM MQ resource adapter, some features of IBM MQ are unavailable or limited.

The IBM MQ resource adapter has the following limitations:
  • Since IBM MQ 8.0, the resource adapter is a Java Platform, Enterprise Edition 7 (Java EE 7) resource adapter providing JMS 2.0 function. Consequently, the IBM MQ 8.0 or later resource adapter must be installed in a Java EE 7 or later certified application server. It can connect in client or bindings transport mode to any in-service queue manager.
  • When running inside the WebSphere® Application Server Liberty application server, the stabilized IBM MQ classes for Java are not supported. Within other application servers the IBM MQ classes for Java are not recommended for use. See the IBM technote Using WebSphere MQ Java Interfaces in J2EE/JEE Environments for details of IBM MQ classes for Java considerations within Java EE.
  • When running inside the WebSphere Application Server Liberty application server on z/OS®, the wmqJmsClient-2.0 feature must be used. Generic JCA support is not possible for z/OS.
  • The IBM MQ resource adapter does not support channel exit programs that are written in languages other than Java.
  • While an application server is running, the value of the sslFipsRequired property must be true for all JCA resources or false for all JCA resources. This is a requirement even if the JCA resources are not used concurrently. If the sslFipsRequired property has different values for different JCA resources, IBM MQ issues the reason code MQRC_UNSUPPORTED_CIPHER_SUITE, even if a TLS connection is not being used.
  • You cannot specify more than one keystore for an application server. If connections are made to more than one queue manager, all the connections must use the same keystore. This limitation does not apply to WebSphere Application Server.
  • If you use a client channel definition table (CCDT) with more than one suitable client connection channel definition, in the event of a failure the resource adapter might select a different channel definition and therefore a different queue manager from the CCDT, which would cause problems for transaction recovery. The resource adapter does not take any action to prevent such a configuration from being used, and it is your responsibility to avoid configurations that might cause problems for transaction recovery.
  • The connection retry functionality introduced in IBM WebSphere MQ 7.0.1 is not supported for outbound connections when running in a Java EE container (EJB/Servlet). Connection retry is not supported at all for outbound JMS when the adapter is used in a JEE container context, regardless of transaction configuration or for non-transacted use.
  • Re-authentication, as defined in Section 9.1.9 of the Java EE Connector Architecture version 1.7 specification, of JMS connections is not supported. The ra.xml file within the IBM MQ resource adpater must have the property called reauthentication-support set to the value false. An attempt by the application server to re-authenticate a JMS connection results in the IBM MQ resource adapter throwing a javax.resource.spi.SecurityException with the MQJCA1028 message code.