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

Batch activity "System-Queue-.ProcessBatch" threw: com.pega.pega



When running the NBAM programs, system administrator is seeing lots of NullPointerException in the pega logs.
These exceptions are very frequent as the number of programs executed every day is large.

Error Messages

2015-04-15 09:25:32,792 [ PegaRULES-Batch-2] [ STANDARD] [ PegaNBAM:06.03] (ernal.async.BatchRequestorTask) ERROR - Batch activity "System-Queue-.ProcessBatch" threw: PRRuntimeError
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.doWithRequestorLocked(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
Caused by: java.lang.NullPointerException
at com.pegarules.generated.activity.ra_action_applicationsetup_20d0ee9e7f9348066b05272952a72b00.step1_circum0(
at com.pegarules.generated.activity.ra_action_applicationsetup_20d0ee9e7f9348066b05272952a72b00.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
... 11 more

Steps to Reproduce

Run an NBAM program.
Check the Pega log files.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. The issue was observed after the installation of hot fix HFix-6308. This hot fix introduces a prConfig variable: 
         <env name="initialization/childrequestors/uselightweightauth" value="false" />

If the new setting is set to ‘false’ it causes the requestor to perform a full-fledged authorization. Since the execution of the program run is performed by a batch agent with child requestors created to process offers, the Operator information will not be available and hence we get the


This issue is resolved by hotfix item Hfix-21886.


Published June 12, 2015 - 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