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

Exception while processing application and agent failure

SA-19059

Summary



User reported that agent failed with error 'java.lang.NoClassDefFoundError: com/pega/apache/log4j/spi/ThrowableInformation'.


Error Messages



Exception at 20151217T053412.907 GMT: java.lang.NoClassDefFoundError: com/pega/apache/log4j/spi/ThrowableInformation 
at com.pega.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:155) 
at com.pega.apache.log4j.Category.forcedLog(Category.java:391) 
at com.pega.apache.log4j.Category.error(Category.java:322) 
at com.pega.pegarules.priv.LogHelper.error(LogHelper.java:1345) 
at com.pegarules.generated.activity.ra_action_processexternalfeeds_f6593ab9f5a4dd7b1856704283c0a4e9.step4_3_circum0(ra_action_processexternalfeeds_f6593ab9f5a4dd7b1856704283c0a4e9.java:1187) 
at com.pegarules.generated.activity.ra_action_processexternalfeeds_f6593ab9f5a4dd7b1856704283c0a4e9.step4_0_circum0_AEXP_FW_Ent_Int_SQL_GNA_ACQ_APP_UPD_DTL(ra_action_processexternalfeeds_f6593ab9f5a4dd7b1856704283c0a4e9.java:516) 
at com.pegarules.generated.activity.ra_action_processexternalfeeds_f6593ab9f5a4dd7b1856704283c0a4e9.perform(ra_action_processexternalfeeds_f6593ab9f5a4dd7b1856704283c0a4e9.java:146) 
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375) 
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:719) 
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:600) 
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:885) 
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177) 



Steps to Reproduce


Not Applicable.


Root Cause



A defect or configuration issue in the operating environment. During this time noticed there were some transaction related error which caused all the database operations fail, hence above error.

Resolution



Here’s the explanation for the reported behavior:

Below prconfig.xml or DSS setting help to preload the engine classes, but does not address the underlying problem. ThrowableInformation and StackTrace are common classes to preload.

prconfig.xml setting:
--------------------------------

prconfig.xml setting: initialization/preloadengineclasses
Value: com.pega.pegarules.priv.util.StackTrace com.pega.apache.log4j.spi.ThrowableInformation
 
Note: Classes are separated by space.

DSS setting:
------------------

To set via DSS - refer https://pdn.pega.com/how-set-prconfig-values-dynamic-system-setting-value
 
Ruleset:  Pega-Engine
Purpose: prconfig/initialization/preloadengineclasses/default
Value: com.pega.pegarules.priv.util.StackTrace com.pega.apache.log4j.spi.ThrowableInformation
 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% 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