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

Classloading issues with Pega 7.1.7 EAR deployment in WebSphere

SA-19363

Summary



Application server logs start showing ​NoClassDefFoundErrors for many java classes after some hours from server start.
The issue is occurring on a Pega 7.1.7 multinode deployment on WebSphere 8.5.5.4
The issue is resolved on server restart.

User Environment Details

  • Pega 7.1.7
  • WebSphere 8.5.5.4
  • Oracle Database 11g

Error Messages



java.lang.ClassNotFoundException: com.pega.apache.axis2.AxisFault
    at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.findClass(PRBaseLoader.java:312)
    at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:773)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:750)
    at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.loadClass(PRBaseLoader.java:237)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:727)
    at com.pega.pegarules.bootstrap.loader.PRAppLoader.loadClass(PRAppLoader.java:796)
    at com.pega.pegarules.bootstrap.loader.PRAppLoader.loadClass(PRAppLoader.java:659)
    at com.pega.pegarules.exec.internal.util.classloader.PRClassLoaderDB.loadClass(PRClassLoaderDB.java:1034)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:727)
    at com.pega.pegarules.exec.internal.util.classloader.PRClassLoaderDB$Loader.loadClass(PRClassLoaderDB.java:2038)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:727)
    ... 107 more


Steps to Reproduce



Restart a server and monitor application logs


Root Cause



A defect in Pegasystems’ code or rules: Pega stores extracted classes in the following temp folder: /extractedFiles/apploader

Due to an issue in the EAR deployment, in Websphere, this folder is incorrectly created under the JVM temp directory instead of the Pega temp directory. In this case, if there are different Pega JVMs running on the same machine, another Pega JVM can overwrite the extracted classes, which causes anything that relies on those classes to produce a NoClassDefFoundError such as the one observed.
This issue has been addressed in Pega 7.1.8 release. 

Resolution



Make the following change to the operating environment: Please apply the environment change described in the following PDN Article: https://pdn.pega.com/node/1003611
Suggest Edit

Published February 26, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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