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

LibraryFunctionNotFoundException post Pega 7.3.1



The com.pega.apache.log4j package fails to load. This occurs after upgrading from Pega 7.1.7 to Pega 7.3.1 running on JBoss EAP 7.0.9 with IBM java version 1.8.0_151.

Error Messages

[ default task-38] [TABTHREAD1] [ ] [ PEGA:02.03.01] ( internal.mgmt.Executable) ERROR pegarsa01| pegaoper1 - Exception Failed to extract 'pega_pegautilities'
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection( ~[prprivate.jar:?]

Steps to Reproduce

  1. Create a custom library in Pega 7.1.7.
  2. Import the com.pega.apache.log4j package
  3. Use com.pega.apache.log4j.Logger.getLogger method in a custom function.
  4. Upgrade to Pega 7.3.1.
  5. Compile the custom library created in Pega 7.1.7.

Root Cause

An issue in the custom application code or rules. Apache Log4j 1 logging service is upgraded to the Apache Log4j 2 logging service in Pega 7.3 platform. However, the custom code in function points to the old package name, com.pega.apache.log4j. 


Perform the following local-change:

Update the package name from com.pega.apache.log4j to org.apache.logging.log4j

Published October 9, 2018 - 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