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

Pega Procom SLA agent displays NullPointerException

SA-82842

Summary



Pega-ProCom SLA Agent displays NullPointerException when processing records from the System Queue.


Error Messages



<pxErrorMessage>error message not specified</pxErrorMessage>
<pxStackTrace>java.lang.NullPointerException
at com.pega.pegarules.data.internal.dictionary.ClassInfoImpl.getRuleSet(ClassInfoImpl.java:2972)
at com.pega.pegarules.session.internal.authorization.Authorization.getAccessGroupsForClass(Authorization.java:1502)
at com.pega.pegarules.session.internal.authorization.Authorization.determineAccessGroupToUse(Authorization.java:2243)
at com.pegarules.generated.activity.ra_action_establishcontext_e7f18093e614322ab46b6816bc8ceb2a.step5_circum0(ra_action_establishcontext_e7f18093e614322ab46b6816bc8ceb2a.java:589)
at com.pegarules.generated.activity.ra_action_establishcontext_e7f18093e614322ab46b6816bc8ceb2a.perform(ra_action_establishcontext_e7f18093e614322ab46b6816bc8ceb2a.java:150)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3421)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:786)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:568)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:1057)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1357)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1105)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:986)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:763)
at com.pega.pegarules.session.internal.async.Agent.queueBatchActivityForAgent(Agent.java:1546)
at com.pega.pegarules.session.internal.async.Agent.queueBatchActivityForAgent(Agent.java:1315)
at com.pega.pegarules.session.internal.async.AgentQueue.run(AgentQueue.java:943)
at com.pega.pegarules.session.internal.async.Agent.runAgentTask(Agent.java:959)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:236)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:171)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:274)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)
at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:246)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:33)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.invokeEngine(Unknown Source)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:155)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.onMessage(PRAsync.java:112)
at sun.reflect.GeneratedMethodAccessor156.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273)
at com.pega.pegarules.internal.etier.mdb.PRAsyncBoot.onMessage(PRAsyncBoot.java:91)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:438)
at weblogic.ejb.container.internal.MDListener.run(MDListener.java:671)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
</pxStackTrace>



Steps to Reproduce

  1. Create a work object with an overall SLA.
  2. Change the overall SLA by invoking the pxAdjustSLA activity. After the Goal event, a new record is added to the broken queue.


Root Cause



A defect in Pegasystems’ code or rules.
The user's application had the Pega Marketing application as a dependency. The Pega Marketing application had overridden two final activities from the  Pega Platform. Therefore, new features introduced in the Pega Platform were overridden.



Resolution



Apply HFix-54000.

Published August 19, 2019 - 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