Limitations of the IBM MQ resource adapter

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:
  • The IBM MQ resource adapter is supported on all IBM MQ platforms, except 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 an SSL 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 JEE 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.