Support Article
External classes are not resolved in JBOSS EAP 6.1
SA-22085
Summary
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
- Place external jar files in JBOSS path /opt/JBossEAP611/jboss-eap-6.1/standalone/lib.
- 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.
Resolution
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 :
prpc_j2ee14_jboss61JBM\META-INF\jboss-deployment-structure.xml
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">
<dependencies>
<module name="org.jboss.remote-naming"/>
<module name="org.hornetq"/>
<module name=”foo”/>
</dependencies>
<resources>
<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" />
</resources>
</sub-deployment>.
Published May 25, 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.