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

NPE after running Program post NBAM 7.12 upgrade



Administrator has reported that they are getting a NullPointerException in PegaRULES logs when they try to execute a NBAM Program after they upgraded NBAM from 7.11 (on Pega7.1.6) to 7.12 (with Pega7.1.7).

Error Messages

2015-01-21 12:04:07,039 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PegaNBAM:07.12] (cessBatch.System_Queue_.Action) ERROR - One of the child requestors failed in running offer flows in batch.

at com.pegarules.generated.activity.ra_action_processbatch_c1b5729a35ab5e76d228f010ec539f43.step2_circum0(
at com.pegarules.generated.activity.ra_action_processbatch_c1b5729a35ab5e76d228f010ec539f43.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(

Steps to Reproduce

  1. Launch NBAM portal.
  2. Create NBAM Program in NBAM 7.12 Upgraded environment.
  3. Analyze the log files

Root Cause

The root cause of the NullPointerException was due to a non out-of-the-box version of the activity ExecuteProgramRun which was having a Page-Copy step missing. During comparison of the Tracer from behaviour reported environment with in house local upgraded environment, it was evident that non-working version on an Activity rule was created by an Operator ID - [email protected] and saved in PegaNBAM-Artifacts:07-11-01. This custom rule was causing the NullPointerException


Deleted the problematic version (custom) of activity rule ExecuteProgramRun (present in PegaNBAM-Artifacts:07-11-01 in the issue reported environment) which was not having a Page-Copy step. This step is present in the out-of-the-box version of the activity ExecuteProgramRun.

Published January 31, 2016 - Updated December 2, 2021

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