We have used consumeJMS in NiFi ( CFM 2.1.5.0-215) in the past with traditional monolithic jars from IBM that had all the classes: dhbcore-7.5.jar ESBSSLReader.jar jboss-common-4.0.0.jar jboss-j2ee-4.0.0.jar jms.jar mq-8.0.0.4.jar mq.allclient-8.0.0.4.jar mq.commonservices-8.0.0.4.jar mq.headers-8.0.0.4.jar mq.jmqi-8.0.0.4.jar mqjms-8.0.0.4.jar The new client does not use these jars. From the IBM documentation for 9.3.5 client, it seems NiFi is using a "modular" configuration if I read things correctly. It has the warning: Note: If you have applications that use the available JAR files in a modular context by relying on the default module names, you must update your applications to require the new module names. The default module names are derived from the JAR file names. Followed by: You can configure your modular application to use IBM MQ classes for JMS (com.ibm.mq.allclient.jar) by completing the following steps: Configure the application to require the com.ibm.mq.javax module. Configure the application to include the MQ_HOME/java/lib/modules/javax directory in the module-path.
... View more
