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

External classes are not resolved in JBOSS EAP 6.1



User is migrating application in Pega 7.1.6 from Websphere Application Server to JBOSS EAP 6.1 with some external jar files kept in JBOSS application server.

The classes in external jar files are not resolved by Pega during runtime.

Error Messages

java.lang.NoClassDefFoundError: /requester/config/Configuration

Steps to Reproduce

  1. Place external jar files in JBOSS path /opt/JBossEAP611/jboss-eap-6.1/standalone/lib.
  2. From a java step in an activity, try to access classes in the Jar file.

Root Cause

User should follow the steps required to create custom modules in JBoss EAP 6.


Perform the following local-change steps:

1. Refer to Redhat Support Portal for use in custom modules with JBoss. For Pega, add the custom module in the following file :

2. Redeploy the .ear

The file change is to add the module to the dependency of both prweb.war and prbean.jar.

Example (replace ‘foo’ with your module name):

<sub-deployment name="prweb.war">
<module name="org.jboss.remote-naming"/>
<module name="org.hornetq"/>
<module name=”foo”/>
<resource-root path="APP-INF/lib/prbootstrap.jar" />
<resource-root path="APP-INF/lib/prresources.jar" />
<resource-root path="APP-INF/lib/prbootstrap-api.jar" />

Published May 25, 2016 - Updated October 8, 2020

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