Support Article

MQ Connect setup with JBoss EAP 6.3 does not work



Upgraded to JBoss EAP 6.3 and deployed prweb.war 7.17 but IBM's Messaging Queue (MQ) connectivity does not work. Prior success on EAP 5.1.2 was achieved.
The MQ jars are deployed along with prweb.war file to JBoss deployment directory for Pega application profile.

Error Messages


Steps to Reproduce

Start Pega application (try both prweb.war and the EAR) on JBoss EAP 6.3.

Root Cause

Pega is deployed on EAP 6 and MQ drivers are deployed in to Pega installation. The Pega classloader is unable to locate them.

JBoss EAP 6 does not utilize or support a lib or directory for loading libraries onto the classpath. EAP 6 classloading employs the JBoss modules project.


Make the MQ drivers into a module and configure it be to a global module. A global module is available to all deployments in EAP 6.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.