PegaMktUtilities Libraries not compiling
The Pega NBAFS Production Environment did not compile the PegaMKTUtilities library. As such many of the core functionalities failed to function.
2016-04-03 09:00:18,551 [fault (self-tuning)'] [TABTHREAD0] [ ] [ PegaNBAFS:07.11.01] ( internal.mgmt.Executable) ERROR <your hostname | ip> NBAFSSysAdmin - FirstUseAssemblerException
com.pega.pegarules.pub.generator.FirstUseAssemblerException: Failed to compile generated Java com.pegarules.generated.activity.ra_action_completeassignment_51806d9c214cddba05dab1553da9e3e7: ----------
1. ERROR in com/pegarules/generated/activity/ra_action_completeassignment_51806d9c214cddba05dab1553da9e3e7.java (at line 2246)
pegamkt_engine_pegamktutilities.StartOfferFlow(refFlowName, myStepPage, tools.getParameterPage());
pegamkt_engine_pegamktutilities cannot be resolved
Steps to Reproduce
Use the application.
A defect or configuration issue in the operating environment, there were two PRPC applications deployed on the same weblogic but in different cluster with each cluster having two servers each. One application was CPMFS and other is NBAFS, on which the current issue is seen.
The issue gets resolved after regenerating the library, however in the PRGenJava directory in Pega temp directory, the timestamps of the generated library java files did not change.
Regenerating the libraries in NBAFS application introduces library assembly errors in CPMFS application and vice versa. User found that the servers are sharing common pega temp directory.
All the weblogic servers "setDomainEnv.sh" file had "-Dpega.tmpdir" jvm argument set to the same directory.
Perform the following local-change:
Use dedicated Pega temp directory for each PRPC jvms.
Update -Dpega.tmpdir jvm argument in the "setDomainEnv.sh" on each weblogic server to point to individual directory location.
0% found this useful