Classloading-Issue with MQ driver com.ibm.mq:wmq.jakarta.jmsra:9.4.0.5 in Wildfly 32

we are facing an issue while using the Java MQ driver in Version 9.4.0.5 (also for 9.4.0.0) in Wildfly 32.0.1.Final as documented here (https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/7.4/html-single/configuring_messaging/index?extIdCarryOver=true&sc_cid=701f2000001OH7TAAW#deploy_the_ibm_mq_resource_adapter).

When trying to connect to the MQ server, we see the following stacktrace in the log file (for the complete stacktrace please refer to the attached log file):

Caused by: java.lang.NullPointerException: Cannot invoke "java.net.URL.openStream()" because "resource" is null at deployment.wmq.jakarta.jmsra9.4.0.5.rar//com.ibm.mq.jmqi.CipherSpecBean.getCiphers(CipherSpecBean.java:166)at deployment.wmq.jakarta.jmsra-9.4.0.5.rar//com.ibm.mq.jmqi.CipherSuiteUtils.<clinit>(CipherSuiteUtils.java:157)

... 154 more

As we are not the alone with this issue (see https://stackoverflow.com/questions/77241592/getting-a-nullpointerexception-error-when-starting-application-using-resource-ad), we assume that the mentioned MQ driver uses, when deployed as rar file inside the deployments directory of the Wildfly application server, not the correct ClassLoader.

Our assumption is underlined by the fact that when we deploy a simple jar file which only contains the ciphermappings.json file from the com.ibm.mq.jmqi.jar as a Wildfly module inside the modules folder, the file is found and the issue disappears. This strongly indicates that using a different class loader inside the MQ driver will allow to deploy the MQ driver rar inside Wildfly’s deployments folder as described in Red Hat’s documentation (link above).

Many thanks in advance for addressing this issue in the near future.

Please find attached the Wildfly log, the Wildfly configuration file as well as the MQ trace file.