Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

ClassNotFoundException in JNDI lookup of remote JMS CF



In a Pega Platform 8.1.1 application deployed on JBoss EAP 7.1, a remote JMS Connection Factory exposed by a different JBoss EAP 7.1 application server (AS) instance is looked up.
The resources exposed by the remote application server are configured correctly. A plain Java client application is used to resolve the required resources and messages are sent or received to/from the remote destination.
In the Pega application, Java Naming and Directory Interface (JNDI) Server and Java Message Service (JMS) Connector rules are created. However, error occurs while testing the connectivity from the JMS Connector rule.

Error Messages

JNDI lookup of JMS connection factory 'jms/RemoteConnectionFactory' failed: javax.naming.NamingException: Failed to lookup [Root exception is java.lang.ClassNotFoundException: org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory]

Steps to Reproduce

  1. Create and configure a JNDI Server rule to address the remote JBoss JNDI server.
  2. Create a JMS Producer Module with a Point-to-Point domain.
  3. Create and configure a JMS Connector using Direct JNDI Lookup.
  4. Manually input the Connection Factory JNDI name.
  5. Click Test Connectivity. Exception occurs.

Root Cause

A defect or configuration issue in the operating environment.

Since the remote JMS integration scenario involved the same application server version, additional JMS client libraries need not be imported because the application server already provided the required libraries.
However, the existing ActiveMQ Artemis libraries provided by JBoss must be exposed in the application classpath.
When this step is not performed, a ClassNotFoundException occurred during the unmarshalling of the remote JNDI reference retrieved through the JNDI lookup.


Make the following change to the operating environment:

Edit the JBoss EAP 7.1 configuration file in use (standalone-[full|ha].xml or domain.xml) to add a global module which exposes the ActiveMQ Artemis libraries to deploy applications.

For example,

<subsystem xmlns="urn:jboss:domain:ee:4.0">
        <module name="org.apache.activemq.artemis" slot="main"/>

Published May 9, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us