Support Article
No functions found for library, Engine failed to start
SA-12051
Summary
After restarting the JVM, PegaRULES engine initialization failed.
Error Messages
2015-07-07 17:42:07,356 [] [ STANDARD] [ ] (ary.LibraryFunctionUtilityImpl) WARN - No functions found for library: TESTLIBRARY
2015-07-07 17:42:07,362 [] [ STANDARD] [ ] (ary.LibraryFunctionUtilityImpl) WARN - No functions found for library: TESTLIBRARY(SFRCRP)
2015-07-07 17:42:07,731 [] [ STANDARD] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: TestServer
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:387)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1596)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl$1.run(EngineImpl.java:143)
at java.security.AccessController.doPrivileged(AccessController.java:273)
at java.lang.reflect.Method.invoke(Method.java:611)
...
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1700)
Caused by:
com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1092)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:798)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
... 88 more
Caused by:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1090)
... 90 more
Caused by:
java.lang.NullPointerException
at com.pega.pegarules.generation.internal.library.LibraryUtilityBase.getUniqueGeneratedClassName(LibraryUtilityBase.java:408)
at com.pega.pegarules.generation.internal.library.LibFunctionDef.<init>(LibFunctionDef.java:203)
at com.pega.pegarules.generation.internal.library.LibLibraryDef.buildFunctionTree(LibLibraryDef.java:275)
at com.pega.pegarules.generation.internal.library.LibraryFunctionUtilityImpl.generateAllFunctionsForLibrary(LibraryFunctionUtilityImpl.java:1277)
at com.pega.pegarules.generation.internal.library.LibraryFunctionUtilityImpl.generateLibrary(LibraryFunctionUtilityImpl.java:930)
at com.pega.pegarules.generation.internal.library.LibraryFunctionUtilityImpl.extractAll(LibraryFunctionUtilityImpl.java:403)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.handleExtraction(PRNodeImpl.java:1918)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:505)
Steps to Reproduce
Restart JVM.
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment. After adding DEBUG to following Pega Java packges:
com.pega.pegarules.generation.internal.library
com.pega.pegarules.pub.clipboard
There was an issue identified with custom library and function added to this environment before starting the JVM.
Resolution
This issue is resolved through the following local change: After deleting the custom library and function from pr4_base table and clearing the Pega temp directory from Application server resulted in clean startup of the engine.
Published July 14, 2015 - 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.