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

NoClassDefFound in AES when sending emails



AES encounters NoClassDefFound exceptions when attempting to send an email, such as scorecards or email notifications.

Error Messages

2015-11-03 09:56:36,108 [.PRPCWorkManager : 4] [  STANDARD] [           AES:07.10] ( SystemAgentFixer.Code_.Action) INFO    - Started agent PegaAES-Data-IndicatorComp.MonitorIndicators
2015-11-03 09:56:36,452 [.PRPCWorkManager : 4] [ STANDARD] [ AES:07.10] (ernal.async.BatchRequestorTask) ERROR - Batch activity "PegaAES-Data-IndicatorComp.MonitorIndicators" threw:
java.lang.NoClassDefFoundError: com.pega.apache.http.auth.AuthSchemeFactory
at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.getServiceUtilsPriv(
at com.pega.pegarules.session.internal.mgmt.Executable.getServiceUtilsPriv(
at com.pegarules.generated.SendEmailMessage_071015_ai7uXdDX6AsHbgtRqmJ0uw.SendEmailMessage07_10_15(
at com.pegarules.generated.SendEmailMessage_071015_ai7uXdDX6AsHbgtRqmJ0uw.invoke(
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(
at com.pegarules.generated.pega_integrationengine_default.SendEmailMessage(
at com.pegarules.generated.activity.ra_action_sendemailnotification_68866db51912c270f78c29e148aa5c65.step6_circum0(
at com.pegarules.generated.activity.ra_action_sendemailnotification_68866db51912c270f78c29e148aa5c65.perform(


Steps to Reproduce

Not Applicable

Root Cause

Pega stores extracted classes in the following temp folder:

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.


Explicitly specify the folder for the extracted files. To do so, add the following in the JVM arguments:

Published January 31, 2016 - 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