Support Article
Problem during Application Profile archive import
SA-330
Summary
You are trying to import an Application Profile (AP) archive that fails with below error in PegaRULES log.
Application Profile viewer (in progress) does not show this AP and it is not reported in a report definition on appropriate class viz PegaAccel-Task-ABCApp
Error Messages
2014-07-23 15:37:59,785 [j2ee14_ws,maxpri=10]] [ STANDARD] [ XYZZY:01.01.02] (ga_importexport_pximportexport) ERROR - ImportArchive: Encountered the following error: null
java.lang.NullPointerException
at com.pegarules.generated.activity.ra_action_checkformismatch_4c8c91701f66b5f6fcf04ac61a7112f8.step2_circum0(ra_action_checkformismatch_4c8c91701f66b5f6fcf04ac61a7112f8.java:496)
at com.pegarules.generated.activity.ra_action_checkformismatch_4c8c91701f66b5f6fcf04ac61a7112f8.perform(ra_action_checkformismatch_4c8c91701f66b5f6fcf04ac61a7112f8.java:95)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:2889)
at com.pega.pegarules.exec.internal.declare.infengine.ChainingEngineUtilImpl.runActivity(ChainingEngineUtilImpl.java:217)
at com.pega.pegarules.exec.internal.declare.infengine.TriggerImpl.evaluateNetworks(TriggerImpl.java:260)
at com.pega.pegarules.data.internal.access.DatabaseImpl.performTriggers(DatabaseImpl.java:11746)
at com.pega.pegarules.data.internal.access.DatabaseImpl.performCommitTriggers(DatabaseImpl.java:2437)
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2283)
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2164)
at com.pega.pegarules.data.internal.access.DatabaseImpl.commit(DatabaseImpl.java:1921)
at com.pega.pegarules.deploy.internal.util.ImportImpl.issueCommit(ImportImpl.java:1429)
at com.pega.pegarules.deploy.internal.util.ImportImpl.importContents(ImportImpl.java:1178)
at com.pega.pegarules.deploy.internal.util.ImportImpl.performImport(ImportImpl.java:1545)
at com.pega.pegarules.deploy.internal.util.ImportImpl.performImport(ImportImpl.java:1473)
at com.pega.pegarules.deploy.internal.util.ImportImpl.importArchive(ImportImpl.java:873)
at com.pega.pegarules.deploy.internal.util.ImportImpl.importPegaArchive(ImportImpl.java:1453)
at com.pega.pegarules.deploy.internal.archive.PegaArchiveAbstract.doImport(PegaArchiveAbstract.java:323)
at com.pegarules.generated.pxImportArchive_060201_OJxD6VU15TYjlV46nBfmsw.pxImportArchive06_02_01(pxImportArchive_060201_OJxD6VU15TYjlV46nBfmsw.java:140)
at com.pegarules.generated.pxImportArchive_060201_OJxD6VU15TYjlV46nBfmsw.invoke(pxImportArchive_060201_OJxD6VU15TYjlV46nBfmsw.java:82)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:131)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:108)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:7749)
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflection(LibrarySupport.java:181)
at com.pegarules.generated.pega_importexport_pximportexport.pxImportArchive(pega_importexport_pximportexport.java:241)
at com.pegarules.generated.activity.ra_action_pegarulesmove_zip_to_db_7285545804e018054ae2b072e254f94c.step6_circum0(ra_action_pegarulesmove_zip_to_db_7285545804e018054ae2b072e254f94c.jav
Steps to Reproduce
1) Package an AP
2) Import the AP zip into another instance. The import is reported successful on the UI
3) The application profile viewer does not show this AP and it is not reported in the report definition on class PegaAccel-Task-ABCApp
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules.
The PegaSaveDetect diagnostic patch is interfering with the successful import of the AP archive.
Resolution
This issue is resolved through the following local change:
There are two Dynamic System Settings that are used for the PegaSaveDetect tool.
The owning RuleSet is Pega-ProCom. The purposes of this DSS are PegaSaveDetect/TrackSaves and PegaSaveDetect/TrackDeletes .
Set both of these to false and the import will be successful.
Set them back to true to reactivate the diagnostic tool.
Published March 12, 2016 - 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.